- 18 Jul, 2014 22 commits
-
-
H Hartley Sweeten authored
The comedi_error() function is just a wrapper around dev_err() that adds the dev->driver->driver_name prefix to the message and a terminating new-line character. The addition of the driver_name is just added noise and some of the users of comedi_error() add unnecessary additional new-line characters. Use dev_err() directly instead of comedi_error() to avoid any confusion and so that all the comedi generated kernel messages have the same format. Signed-off-by:
H Hartley Sweeten <hsweeten@visionengravers.com> Cc: Ian Abbott <abbotti@mev.co.uk> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
H Hartley Sweeten authored
The comedi_error() function is just a wrapper around dev_err() that adds the dev->driver->driver_name prefix to the message and a terminating new-line character. The addition of the driver_name is just added noise and some of the users of comedi_error() add unnecessary additional new-line characters. Use dev_err() directly instead of comedi_error() to avoid any confusion and so that all the comedi generated kernel messages have the same format. Signed-off-by:
-
H Hartley Sweeten authored
The comedi_error() function is just a wrapper around dev_err() that adds the dev->driver->driver_name prefix to the message and a terminating new-line character. The addition of the driver_name is just added noise and some of the users of comedi_error() add unnecessary additional new-line characters. Use dev_err() directly instead of comedi_error() to avoid any confusion and so that all the comedi generated kernel messages have the same format. Signed-off-by:
-
H Hartley Sweeten authored
The comedi_error() function is just a wrapper around dev_err() that adds the dev->driver->driver_name prefix to the message and a terminating new-line character. The addition of the driver_name is just added noise and some of the users of comedi_error() add unnecessary additional new-line characters. Use dev_err() directly instead of comedi_error() to avoid any confusion and so that all the comedi generated kernel messages have the same format. Signed-off-by:
-
H Hartley Sweeten authored
The comedi_error() function is just a wrapper around dev_err() that adds the dev->driver->driver_name prefix to the message and a terminating new-line character. The addition of the driver_name is just added noise and some of the users of comedi_error() add unnecessary additional new-line characters. Use dev_err() directly instead of comedi_error() to avoid any confusion and so that all the comedi generated kernel messages have the same format. Signed-off-by:
-
H Hartley Sweeten authored
The comedi_error() function is just a wrapper around dev_err() that adds the dev->driver->driver_name prefix to the message and a terminating new-line character. The addition of the driver_name is just added noise and some of the users of comedi_error() add unnecessary additional new-line characters. Use dev_err() directly instead of comedi_error() to avoid any confusion and so that all the comedi generated kernel messages have the same format. Signed-off-by:
-
H Hartley Sweeten authored
The kbuild test robot reported a build error on ARCH=arm about implicit declaration of the functions 'kmalloc' and 'kfree'. On ARCH=x86 the slab.h header is indirectly included by pci.h, this does not occur on ARCH=arm. Include slab.h directly instead of relying on some other header to include it. Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
Jes Sorensen <Jes.Sorensen@redhat.com> Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
The value saved in RegBcnCtrlVal was never used. In addition the code was highly endian broken, declaring it as a u32, then accessing it via a u8 * later. Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Raphael Silva authored
Some corrections were made to the code in order to conform to the Kernel Coding Style. Jes: Fix build problem Signed-off-by:
Raphael Silva <rapphil@gmail.com> Signed-off-by:
-
Jes Sorensen authored
Reduce yet another duplicate implementation of set_media_status() Signed-off-by:
-
Jes Sorensen authored
We use the MSR bits to define link state anyway, so no point having an additional two sets of defines for the same thing. Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Eli Billauer authored
The dedicated memory management routines have been replaced with devres API, so the related part is removed from the doc. Signed-off-by:
Eli Billauer <eli.billauer@gmail.com> Signed-off-by:
-
Eli Billauer authored
According to Documentation/CodingStyle, when one branch of an if-else statement has multiple statements, both branches should be enclosed in curly brackets. Signed-off-by:
-
- 16 Jul, 2014 18 commits
-
-
H Hartley Sweeten authored
Fix the checkpatch.pl warning: WARNING: Unnecessary space before function pointer arguments Signed-off-by:
-
H Hartley Sweeten authored
Fix the checkpatch.pl warnings: WARNING: braces {} are not necessary for single statement blocks Signed-off-by: -
H Hartley Sweeten authored
Fix the checkpatch.pl warnings: WARNING: braces {} are not necessary for single statement blocks WARNING: braces {} are not necessary for any arm of this statement Signed-off-by: -
H Hartley Sweeten authored
Fix the checkpatch.pl warning: WARNING: space prohibited before semicolon Signed-off-by:
-
H Hartley Sweeten authored
Fix the checkpatch.pl error: ERROR: trailing whitespace Signed-off-by:
-
H Hartley Sweeten authored
Fix the checkpatch.pl error: ERROR: "(foo*)" should be "(foo *)" Signed-off-by:
-
H Hartley Sweeten authored
Fix the checkpatch.pl warning: WARNING: Prefer kmalloc_array over kmalloc with multiply Signed-off-by:
-
H Hartley Sweeten authored
Fix the checkpatch.pl error: ERROR: Macros with complex values should be enclosed in parenthesis This define is not used in the driver. Just remove it. Signed-off-by:
-
H Hartley Sweeten authored
As indicated by checkpatch.pl, "WARNING: Use of volatile is usually wrong: ...". The variables in the private data that are marked volatile don't need to be. Remove the volatile. Signed-off-by:
-
H Hartley Sweeten authored
As indicated by checkpatch.pl, "WARNING: Use of volatile is usually wrong: ...". The variables in the private data that are marked volatile don't need to be. Remove the volatile. Signed-off-by:
-
H Hartley Sweeten authored
Fix these checkpatch.pl warnings: WARNING: please, no space before tabs Signed-off-by:
-
H Hartley Sweeten authored
As indicated by checkpatch.pl, "WARNING: Use of volatile is usually wrong: ...". The 'bits' parameter to this function does not need to be volatile. Signed-off-by:
-
H Hartley Sweeten authored
As indicated by checkpatch.pl, "WARNING: Use of volatile is usually wrong: ...". The variables in the private data that are marked volatile don't need to be. Remove the volatile. Signed-off-by:
-
H Hartley Sweeten authored
Fix this checkpatch.pl warning: WARNING: space prohibited between function name and open parenthesis '(' Signed-off-by: -
H Hartley Sweeten authored
Fix these checkpatch.pl warnings: WARNING: Possible switch case/default not preceeded by break or fallthrough comment Signed-off-by:
-
H Hartley Sweeten authored
Fix this checkpatch.pl warning: WARNING: Missing a blank line after declarations Signed-off-by:
-
H Hartley Sweeten authored
Fix the checkpatch.pl warnings: WARNING: Missing a blank line after declarations Signed-off-by:
-
H Hartley Sweeten authored
Fix the checkpatch.pl warnings: WARNING: Missing a blank line after declarations Signed-off-by:
-
