[PATCH] staging: lustre: lnet: remove dead code

Remove code which was permanently disabled with ifdefs. This also resolves the following checkpatch warning which was triggered by the dead code: WARNING: space prohibited before semicolon Signed-off-by: Dmitriy Cherkasov ---

[PATCH] hv: fix msi affinity when device requests all possible CPU's

When Intel 10G (ixgbevf) is passed to a Hyper-V guest with SR-IOV, the driver requests affinity with all possible CPU's (0-239) even those CPU's are not online (and will never be). Because of this the device is unable to correctly get MSI interrupt's setup. This was caused by the change in 4.12

Re: [PATCH] staging: speakup: make function ser_to_dev static

Hi, On Wed, Jun 28, 2017 at 02:13:51PM +0100, Colin King wrote: > From: Colin Ian King > > The helper function ser_to_dev does not need to be in global scope, so > make it static. > > Cleans up sparse warning: > "warning: symbol 'ser_to_dev' was not declared. Should

[PATCH] [media] staging/imx: remove confusing IS_ERR_OR_NULL usage

While looking at a compiler warning, I noticed the use of IS_ERR_OR_NULL, which is generally a sign of a bad API design and should be avoided. In this driver, this is fairly easy, we can simply stop storing error pointers in persistent structures, and change the one function that might return

[PATCH] staging: ks7010: fix spelling mistake: "errror" -> "error"

From: Colin Ian King Trivial fix to spelling mistake in netdev_err message Signed-off-by: Colin Ian King --- drivers/staging/ks7010/ks_wlan_net.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH] staging: speakup: make function ser_to_dev static

walter harms, on mer. 28 juin 2017 16:49:03 +0200, wrote: > Am 28.06.2017 15:13, schrieb Colin King: > > diff --git a/drivers/staging/speakup/spk_ttyio.c > > b/drivers/staging/speakup/spk_ttyio.c > > index 442f191a017e..ed8e96b06ead 100644 > > --- a/drivers/staging/speakup/spk_ttyio.c > > +++

Re: [PATCH] staging: speakup: make function ser_to_dev static

Am 28.06.2017 15:13, schrieb Colin King: > From: Colin Ian King > > The helper function ser_to_dev does not need to be in global scope, so > make it static. > > Cleans up sparse warning: > "warning: symbol 'ser_to_dev' was not declared. Should it be static?" > >

[PATCH] staging: speakup: make function ser_to_dev static

From: Colin Ian King The helper function ser_to_dev does not need to be in global scope, so make it static. Cleans up sparse warning: "warning: symbol 'ser_to_dev' was not declared. Should it be static?" Signed-off-by: Colin Ian King ---

Re: [PATCH v4] staging: vboxvideo: Add vboxvideo to drivers/staging

On Wed, Jun 28, 2017 at 2:46 PM, Hans de Goede wrote: > On 27-06-17 06:25, kbuild test robot wrote: >> >> Hi Hans, >> >> [auto build test ERROR on staging/staging-testing] >> [also build test ERROR on v4.12-rc7 next-20170626] >> [if your patch is applied to the wrong git

Re: [PATCH] staging: rts5208 : Fixing coding style warnings

Hi, On Wed, Jun 28, 2017 at 2:50 PM, Simo Koskinen wrote: > Fixed following warnings found by checkpatch.pl script: > > WARNING: Prefer using '"%s...", __func__' to using '', > this function's name, in a string > > Signed-off-by: Simo Koskinen > ---

Re: [PATCH] staging: rts5208 : Fixing coding style warnings

On Wed, Jun 28, 2017 at 02:50:12PM +0200, Simo Koskinen wrote: > Fixed following warnings found by checkpatch.pl script: > > WARNING: Prefer using '"%s...", __func__' to using '', > this function's name, in a string > > Signed-off-by: Simo Koskinen Is this different

[PATCH] staging: rts5208 : Fixing coding style warnings

Fixed following warnings found by checkpatch.pl script: WARNING: Prefer using '"%s...", __func__' to using '', this function's name, in a string Signed-off-by: Simo Koskinen --- drivers/staging/rts5208/rtsx.c | 2 -- drivers/staging/rts5208/rtsx_chip.c | 4 ++--

Re: [PATCH v4] staging: vboxvideo: Add vboxvideo to drivers/staging

Hi Michael, On 27-06-17 06:25, kbuild test robot wrote: Hi Hans, [auto build test ERROR on staging/staging-testing] [also build test ERROR on v4.12-rc7 next-20170626] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 4/4] Staging: rtl8712 : ieee80211.c: fixed camelcase coding

On Tue, Jun 27, 2017 at 05:13:39PM +0530, Jaya Durga wrote: > diff --git a/drivers/staging/rtl8712/osdep_intf.h > b/drivers/staging/rtl8712/osdep_intf.h > index 1985423..dac6aed 100644 > --- a/drivers/staging/rtl8712/osdep_intf.h > +++ b/drivers/staging/rtl8712/osdep_intf.h > @@ -29,7 +29,10 @@ >

Re: [PATCH] staging: rts5208 : Fixing coding style warnings

On Wed, Jun 28, 2017 at 11:15:09AM +0200, Simo Koskinen wrote: > Fixed following warnings found by checkpatch.pl script: > > WARNING: Prefer using '"%s...", __func__' to using '', > this function's name, in a string > > Signed-off-by: Simo Koskinen > --- >

Re: [PATCH 0/2] staging: ccree: Fix coding style and remove warnings

Thank you Karthik, On Wed, Jun 28, 2017 at 12:37 PM, wrote: > From: Karthik Tummala > > This patch series fixes coding style and removes the following > checkpatch.pl warnings: > > Prefer using '"%s...", __func__' to using the function's name, > in a

[PATCH 2/2] staging: ccree: Remove braces {} for single statement blocks

From: Karthik Tummala Fixed following checkpatch.pl warning: WARNING: braces {} are not necessary for single statement blocks. Signed-off-by: Karthik Tummala --- drivers/staging/ccree/ssi_aead.c | 38 ++ 1

[PATCH 0/2] staging: ccree: Fix coding style and remove warnings

From: Karthik Tummala This patch series fixes coding style and removes the following checkpatch.pl warnings: Prefer using '"%s...", __func__' to using the function's name, in a string. Braces {} are not necessary for single statement blocks. Rebased on top of

[PATCH 1/2] staging: ccree: Use __func__ instead of function name

From: Karthik Tummala Fixed following checkpatch.pl warning: WARNING: Prefer using '"%s...", __func__' to using the function's name, in a string It is prefered to use '%s & __func__' instead of function name for logging. Signed-off-by: Karthik Tummala

Re: [PATCH v3] staging: vboxvideo: Add vboxvideo to drivers/staging

On Mon, Jun 26, 2017 at 04:55:46PM +0200, Hans de Goede wrote: > >> +int vbox_dumb_create(struct drm_file *file, > >> + struct drm_device *dev, struct drm_mode_create_dumb *args) > >> +{ > >> + int ret; > >> + struct drm_gem_object *gobj; > >> + u32 handle; > >> + > >> +

[PATCH] staging: rts5208 : Fixing coding style warnings

Fixed following warnings found by checkpatch.pl script: WARNING: Prefer using '"%s...", __func__' to using '', this function's name, in a string Signed-off-by: Simo Koskinen --- drivers/staging/rts5208/rtsx.c | 2 +- drivers/staging/rts5208/rtsx_chip.c | 5 +++--

Re: [PATCH] Staging: unisys: visorbus: Fix coding style warning from checkpatch.pl.

Hi, On Wed, Jun 28, 2017 at 4:49 AM, Quytelda Kahja wrote: > Replace the literal function name "visorbus_create_instance" with the format > specifier "%s" so it can be dynamically filled by the __func__ macro. On a general note, I think the actual change or effect is more

答复: [PATCH 1/2] staging: sm750fb: avoid conflicting vesafb

Hi Greg, Is the reason Sudip gave you for the question of "why" sufficient ? This patch is very important for the driver running in the X86 platform. Without this patch, many SM750 graphic chip customers complain the Ubuntu OS can't run well. When they install the OS, the screen will