> This function is called several times during lustre module insert.
> Namely it's called 5 times for 5 types:
> osc, mdc, lov, lmv, mgc.
Will any extra memory accesses matter for the successful execution
in this use case?
> It's not called any more than that, so it's not exactly a super hot-pat
> -Original Message-
> From: Greg KH [mailto:[email protected]]
> Sent: Wednesday, July 27, 2016 2:26 PM
> To: KY Srinivasan
> Cc: [email protected]; [email protected]; linux-
> [email protected]; [email protected]; [email protected];
> dledf...@re
> -Original Message-
> From: Leon Romanovsky [mailto:[email protected]]
> Sent: Tuesday, July 26, 2016 9:25 PM
> To: KY Srinivasan
> Cc: [email protected]; [email protected];
> [email protected]; [email protected];
> [email protected]; sean.he...@
On Wed, Jul 27, 2016 at 09:09:08PM +, KY Srinivasan wrote:
>
>
> > -Original Message-
> > From: Greg KH [mailto:[email protected]]
> > Sent: Tuesday, July 26, 2016 9:41 PM
> > To: KY Srinivasan
> > Cc: [email protected]; [email protected]; linux-
> > r.
> -Original Message-
> From: Greg KH [mailto:[email protected]]
> Sent: Tuesday, July 26, 2016 9:41 PM
> To: KY Srinivasan
> Cc: [email protected]; [email protected]; linux-
> [email protected]; [email protected]; [email protected];
> dledf...@redh
> -Original Message-
> From: [email protected] [mailto:[email protected]]
> Sent: Thursday, June 16, 2016 3:03 PM
> To: Kershner, David A
> Cc: Neil Horman ; driverdev-
> [email protected]; *S-Par-Maintainer
> ; [email protected];
> [email protected]; Bi
On Wed, Jul 27, 2016 at 05:43:27PM +, Kershner, David A wrote:
> > -Original Message-
> > From: [email protected] [mailto:[email protected]]
> > Sent: Thursday, June 16, 2016 3:03 PM
> > To: Kershner, David A
> > Cc: Neil Horman ; driverdev-
> > de...@linuxdriverproje
Hi !
staging ks7010 has a a few completion calls, some of which are using
wait_for_completion_interruptible_timeout(). The key difference
betweeen wait_for_completion_interruptible_timeout() and
wait_for_completion_timeout() is, if I got it right, only that
the former will return on any pen
declared. Should it be static?
but ks_wlan_reset is unused and effectively an empty function so it can be
dropped.
Compile tested with: x86_64_defconfig + CONFIG_STAGING=y
CONFIG_MMC=m, CONFIG_KS7010=m
Patch is against 4.7-rc7 (localversion-next -next-20160727)
drivers/staging/ks7010/ks_wla
ng: symbol
'send_packet_complete' was not declared. Should it be static?
was caused by build dependencies being resolved locally rather
than at device level.
Compile tested with: x86_64_defconfig + CONFIG_STAGING=y
CONFIG_MMC=m, CONFIG_KS7010=m
Patch is against 4.7-rc7 (localversion-next -next
Two proposed fixes for sparse warnings
drivers/staging/ks7010/ks_wlan_net.c:3392:6: warning: symbol
'send_packet_complete'
was not declared. Should it be static?
looking at how it is used I guess it should not be static but
the extern declaration moved into ks_wlan.h
but all the functi
> From: David Miller [mailto:[email protected]]
> Sent: Wednesday, July 27, 2016 1:45
> To: Dexuan Cui
>
> From: Dexuan Cui
> Date: Tue, 26 Jul 2016 07:09:41 +
>
> > I googled "S390 hypervisor socket" but didn't find anything related (I
> > think).
>
> That would be net/iucv/
Thanks for
> From: [email protected] [mailto:netdev-
> [email protected]] On Behalf Of Dexuan Cui
> Sent: Tuesday, July 26, 2016 21:22
> ...
> This is because, the design of AF_HYPERV in the Hyper-V host side is
> suboptimal IMHO (the current host side design requires the least
> change in the
13 matches
Mail list logo
