On 2015년 11월 12일 20:39, Arnd Bergmann wrote:
On Thursday 12 November 2015 19:05:41 glen lee wrote:
Hi arnd,
I appreciate the patches.
I did test this patch series on h/w which is arm based MCU.
From this patch wilc is not working properly. After downloading firmware, the
firmware cannot st
On 2015/11/11, 10:21, "lustre-devel on behalf of Shivani Bhardwaj"
wrote:
>On Wed, Nov 11, 2015 at 4:24 PM, kbuild test robot wrote:
>> Hi Shivani,
>>
>> [auto build test ERROR on staging/staging-testing]
>> [also build test ERROR on v4.3 next-2015]
>>
>> url:
>>https://github.com/0day-c
The PCI-1760 board unique. It uses a outgoing/incoming mailbox programming
sequence to access the hardware. The other boards supported by this driver
use simple register mapping. Including support for the PCI-1760 in this
driver just makes it harder to understand.
Separate out the PCI-1760 support
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, November 12, 2015 4:28 PM
> To: Sell, Timothy C
> Cc: Romer, Benjamin M; driverdev-devel@linuxdriverproject.org; *S-Par-
> Maintainer
> Subject: Re: [PATCH 3/9] staging: unisys: visorinput: use kref r
On 11/12/2015 01:54 PM, Kalle Valo wrote:
Larry Finger writes:
In commit 54328e64047a5 ("rtlwifi: rtl8821ae: Fix system lockups on boot"),
an attempt was made to fix a regression introduced in commit 1277fa2ab2f9
("rtlwifi: Remove the clear interrupt routine from all drivers").
Unfortunately,
On Thu, Nov 12, 2015 at 09:21:14PM +, Sell, Timothy C wrote:
> > -Original Message-
> > From: Greg KH [mailto:gre...@linuxfoundation.org]
> > Sent: Thursday, November 12, 2015 4:12 PM
> > To: Sell, Timothy C
> > Cc: Romer, Benjamin M; driverdev-devel@linuxdriverproject.org; *S-Par-
> >
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, November 12, 2015 4:12 PM
> To: Sell, Timothy C
> Cc: Romer, Benjamin M; driverdev-devel@linuxdriverproject.org; *S-Par-
> Maintainer
> Subject: Re: [PATCH 3/9] staging: unisys: visorinput: use kref r
The major todo for the hfi1 driver in staging is getting rid of the verbs
code duplication between ipath, qib, and now hfi1. The ipath driver has been
deprecated and is going to be deleted soon. So that leaves qib and hfi. To
address this we have proposed rdmavt which will be a common kmod that
On Thu, Nov 12, 2015 at 09:07:24PM +, Sell, Timothy C wrote:
> What should I do with this patchset?
What patchset?
> Some history: it was fixing this one little line in
> drivers/staging/unisys/visorinput/Kconfig that triggered this patchset:
>
> depends on UNISYSSPAR && UNISYS_VISORBU
What should I do with this patchset?
Some history: it was fixing this one little line in
drivers/staging/unisys/visorinput/Kconfig that triggered this patchset:
depends on UNISYSSPAR && UNISYS_VISORBUS && FB
Adding "INPUT" was easy, but it turned out that removing "FB" was hard. ;-(
Re
爱奇艺vip分享QQ群：5650047每天分享一大波爱奇艺会员帐号，看热门大片不花钱！
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Larry Finger writes:
> In commit 54328e64047a5 ("rtlwifi: rtl8821ae: Fix system lockups on boot"),
> an attempt was made to fix a regression introduced in commit 1277fa2ab2f9
> ("rtlwifi: Remove the clear interrupt routine from all drivers").
> Unfortunately, there were logic errors in that patch
On 11/12/2015 08:35 PM, KY Srinivasan wrote:
-Original Message-
From: Denis V. Lunev [mailto:d...@openvz.org]
Sent: Wednesday, November 11, 2015 11:16 PM
To: KY Srinivasan
Cc: rka...@virtuozzo.com; de...@linuxdriverproject.org; linux-
ker...@vger.kernel.org; Andrey Smetanin ;
Haiyang Z
On Wed, Nov 11, 2015 at 2:27 PM, Ranjith Thangavel
wrote:
> BIT macro is used for defining BIT location instead of
> shifting operator - coding style issue
I would not call it a coding style issue.
___
devel mailing list
de...@linuxdriverproject.org
htt
On 11/11/15 15:54, Ranjith Thangavel wrote:
BIT macro is used for defining BIT location instead of
shifting operator - coding style issue
Signed-off-by: Ranjith Thangavel
---
drivers/staging/comedi/drivers/comedi_parport.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --
On 11/11/15 16:27, Ranjith Thangavel wrote:
BIT macro is used for defining BIT location instead of
shifting operator - coding style issue
Signed-off-by: Ranjith Thangavel
---
drivers/staging/comedi/drivers/cb_pcidda.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
On 11/11/15 16:22, Ranjith Thangavel wrote:
BIT macro is used for defining BIT location instead of
shifting operator - coding style issue
Signed-off-by: Ranjith Thangavel
---
drivers/staging/comedi/drivers/ni_65xx.c | 54 +++---
1 file changed, 27 insertions(+), 27
On 11/11/15 16:14, Ranjith Thangavel wrote:
BIT macro is used for defining BIT location instead of
shifting operator - coding style issue
Signed-off-by: Ranjith Thangavel
---
drivers/staging/comedi/drivers/ni_6527.c | 24
1 file changed, 12 insertions(+), 12 deleti
On 11/11/15 15:48, Ranjith Thangavel wrote:
BIT macro is used for defining BIT location instead of
shifting operator - coding style issue
Signed-off-by: Ranjith Thangavel
---
drivers/staging/comedi/drivers/pcmmio.c | 44 +++
1 file changed, 22 insertions(+), 22
> -Original Message-
> From: Denis V. Lunev [mailto:d...@openvz.org]
> Sent: Wednesday, November 11, 2015 11:16 PM
> To: KY Srinivasan
> Cc: rka...@virtuozzo.com; de...@linuxdriverproject.org; linux-
> ker...@vger.kernel.org; Andrey Smetanin ;
> Haiyang Zhang ; Vitaly Kuznetsov
>
> Subj
On Thu, Nov 12, 2015 at 3:25 PM, Dennis Dalessandro
wrote:
> On Thu, Nov 12, 2015 at 08:04:01AM +0200, Or Gerlitz wrote:
>> Dennis, can we have less camelcase sort of speak in this upstream driver?
>> this is linux here not windowZ.
> I plan to just remove this function.
> See: http://www.spinic
On Thu, Nov 12, 2015 at 08:04:01AM +0200, Or Gerlitz wrote:
On Wed, Nov 11, 2015 at 3:39 PM, Dennis Dalessandro
wrote:
On Wed, Nov 11, 2015 at 08:25:35AM +0200, Leon Romanovsky wrote:
On Wed, Nov 11, 2015 at 12:34:37AM -0500, ira.we...@intel.com wrote:
From: Dennis Dalessandro
+int snoop_sen
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Thursday, November 12, 2015 18:41
> To: Dexuan Cui
> Cc: gre...@linuxfoundation.org; linux-ker...@vger.kernel.org;
> de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com;
> jasow...@redhat.com; KY Srinivasan
> Subject: Re:
> -Original Message-
> From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org]
> Sent: Wednesday, November 11, 2015 11:24 AM
> > If you move the variables to the top and have the early return as you
> > suggest,
> then in some CONFIG cases, there will be all those automatic v
On Thursday 12 November 2015 19:05:41 glen lee wrote:
> Hi arnd,
>
> I appreciate the patches.
> I did test this patch series on h/w which is arm based MCU.
> From this patch wilc is not working properly. After downloading firmware,
> the firmware cannot start and it fails.
> I double check this
When Hyper-V host asks us to remove some util driver by closing the
appropriate channel there is no easy way to force the current file
descriptor holder to hang up but we can start to respond -EBADF to all
operations asking it to exit gracefully.
As we're setting hvt->mode from two separate contex
inmsg should be freed in case of on_msg() failure to avoid memory leak.
Signed-off-by: Vitaly Kuznetsov
---
drivers/hv/hv_utils_transport.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/hv/hv_utils_transport.c b/drivers/hv/hv_utils_transport.c
index 24b2766..1d
The crash is observed when a service is being disabled host side while
userspace daemon is connected to the device:
[ 90.244859] general protection fault: [#1] SMP
...
[ 90.800082] Call Trace:
[ 90.800082] [] __fput+0xc8/0x1f0
[ 90.800082] [] fput+0xe/0x10
...
[ 90.800082] []
I'm observing a crash when a utility driver is disabled host side (e.g.
'Guest services' is disabled live) when we have userspace daemon
connected:
[ 90.244859] general protection fault: [#1] SMP
...
[ 90.800082] CPU: 3 PID: 473 Comm: hypervfcopyd Not tainted
4.3.0-rc7_netvsc_noalloc+ #1
As a preparation to reusing outmsg_lock to protect test-and-set openrations
on 'mode' rename it the more general 'lock'.
Signed-off-by: Vitaly Kuznetsov
---
drivers/hv/hv_utils_transport.c | 14 +++---
drivers/hv/hv_utils_transport.h | 2 +-
2 files changed, 8 insertions(+), 8 deletions
"K. Y. Srinivasan" writes:
> From: Dexuan Cui
>
> spinlock is unnecessary here.
> mutex is enough.
Hm, mutex is usually required when we need to sleep and a spinlock is
enough otherwise :-)
Or are you trying to say we don't need to disable interrupts here? In
that can maybe we can just switch
Hi arnd,
I appreciate the patches.
I did test this patch series on h/w which is arm based MCU.
From this patch wilc is not working properly. After downloading firmware, the
firmware cannot start and it fails.
I double check this patch and the previous one(14/20) which works fine.
I cannot find t
32 matches
Mail list logo
