-- Forwarded message --
From: JENET ADARA
Date: Thu, 9 Sep 2021 15:48:31 +0200
Subject:
To: judge.udo@gmail.com
HELLO, DID YOU RECEIVE MY MAIL?
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.o
On Tue, Sep 01, 2020 at 02:06:23PM +0200, antoni.przyby...@wp.pl wrote:
> On 01.09.2020 13:08, Greg KH wrote:
> > On Tue, Sep 01, 2020 at 12:43:11PM +0200, antoniprzybylik wrote:
> > > Such macros are dangerous. Consider following example:
> > > #define GDM_TTY_READY(gdm) (gdm && gdm->tty_dev &&
On Tue, Sep 01, 2020 at 02:06:23PM +0200, antoni.przyby...@wp.pl wrote:
> On 01.09.2020 13:08, Greg KH wrote:
> > On Tue, Sep 01, 2020 at 12:43:11PM +0200, antoniprzybylik wrote:
> > > Such macros are dangerous. Consider following example:
> > > #define GDM_TTY_READY(gdm) (gdm && gdm->tty_dev &&
On 01.09.2020 13:08, Greg KH wrote:
On Tue, Sep 01, 2020 at 12:43:11PM +0200, antoniprzybylik wrote:
Such macros are dangerous. Consider following example:
#define GDM_TTY_READY(gdm) (gdm && gdm->tty_dev && gdm->port.count)
GDM_TTY_READY(a + b)
This macro will be expanded in such
On Wed, Aug 19, 2020 at 02:57:14PM +0800, Hsin-Yi Wang wrote:
> I think you missed this email :)
>
> -- Forwarded message -
> From: Sam Ravnborg
> Date: Tue, Aug 11, 2020 at 4:35 AM
> Subject: Re: [PATCH v14 0/2] Add initial support for slimport anx7625
> To: Xin Ji
> Cc: , Laure
On Fri, Feb 14, 2020 at 07:07:23PM +0530, Shubakar Gowda wrote:
> -- Forwarded message -
> From: Shubakar Gowda
> Date: Fri, 14 Feb 2020 at 19:04
> Subject: GS_FPGABOOT
> To:
>
>
> Hi,
>
> I am trying for Selectmap Programming using the driver gs_fgpaboot, But
> when I load the
On Sun, 03 Nov 2019, Julia Lawall wrote:
The return at line 747 may need an unlock.
Good catch.
...
:: The code at line 747 was first introduced by commit
:: c48c9f7ff32b8b3965a08e40eb6763682d905b5d staging: exfat: add exfat
filesystem code to staging
Indeed, this was the case re
The return at line 747 may need an unlock.
julia
-- Forwarded message --
Date: Sun, 3 Nov 2019 09:21:22 +0800
From: kbuild test robot
To: kbu...@lists.01.org
Cc: Julia Lawall
Subject: [staging:staging-testing 275/291]
drivers/staging/exfat/exfat_super.c:747:5-11: preceding l
On Friday 4 October 2019 13:18:16 CEST Julia Lawall wrote:
> Hello,
>
> Is an unlock needed on line 53?
>
> julia
>
> -- Forwarded message --
> Date: Fri, 4 Oct 2019 19:14:33 +0800
> From: kbuild test robot
> To: kbu...@01.org
> Cc: Julia Lawall
> Subject: [staging:staging-test
Hello,
Is an unlock needed on line 53?
julia
-- Forwarded message --
Date: Fri, 4 Oct 2019 19:14:33 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: [staging:staging-testing 50/59] drivers/staging/wfx/hif_tx.c:53:2-8:
preceding lock on line 38
CC:
You can drop the if on line 3490.
julia
-- Forwarded message --
Date: Tue, 3 Sep 2019 04:28:35 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: [staging:staging-testing 268/273]
drivers/staging/exfat/exfat_super.c:3491:2-7: WARNING: NULL check before
Hello,
Please check whether an unlock is needed before line 386.
thanks,
julia
-- Forwarded message --
Date: Sun, 30 Sep 2018 01:57:53 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: [staging:staging-next 433/443]
drivers/staging/vboxvideo/vbox_mod
On Tue, 11 Sep 2018, Gao Xiang wrote:
> Hi Julia,
>
> There were lkp logs reporting that before, but I have no idea why it is
> reported.
> z_pagemap_global_lock is taken iff (pages = z_pagemap_global), and it is
> unlocked at
>
> > 3883a79a Gao Xiang 2018-07-26 987 if (pages == z_p
Hi Julia,
There were lkp logs reporting that before, but I have no idea why it is
reported.
z_pagemap_global_lock is taken iff (pages = z_pagemap_global), and it is
unlocked at
> 3883a79a Gao Xiang 2018-07-26 987 if (pages == z_pagemap_global)
> 3883a79a Gao Xiang 2018-07-26 988
I don't know if there is a problem here. Please check the lines mentiond
below, ie lines 839 and 1003.
julia
-- Forwarded message --
Date: Tue, 11 Sep 2018 17:17:15 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: [staging:staging-next 118/220]
driv
On Sat, Jan 27, 2018 at 03:09:11PM +0100, Julia Lawall wrote:
>
>
> On Sat, 27 Jan 2018, Dan Carpenter wrote:
>
> > On Sat, Jan 27, 2018 at 02:37:49PM +0100, Julia Lawall wrote:
> > > Please check whether line 212 is reachable from line 198.
> > >
> >
> > No. It's not.
> >
> > > d7e09d039 drive
On Sat, 27 Jan 2018, Dan Carpenter wrote:
> On Sat, Jan 27, 2018 at 02:37:49PM +0100, Julia Lawall wrote:
> > Please check whether line 212 is reachable from line 198.
> >
>
> No. It's not.
>
> > d7e09d039 drivers/staging/lustre/lustre/libcfs/linux/linux-tcpip.c Peng Tao
> > 2013-05-
On Sat, Jan 27, 2018 at 02:37:49PM +0100, Julia Lawall wrote:
> Please check whether line 212 is reachable from line 198.
>
No. It's not.
> d7e09d039 drivers/staging/lustre/lustre/libcfs/linux/linux-tcpip.c Peng Tao
> 2013-05-02 192 nfound = ifc.ifc_len / sizeof(*ifr
Please check whether line 212 is reachable from line 198.
julia
-- Forwarded message --
Date: Sat, 27 Jan 2018 16:00:47 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: [staging:staging-next 446/587]
drivers/staging/lustre/lnet/lnet/lib-socket.c:212:
Hi Julia,
thank you very much for your investigation!
I totally agree - on line 894 device->dev must not be used. Any suggestions? Is
there a kind of generic value, I can pass as first argument of dev_dbg() in such
cases? Or switch to printk()?
Regarding second bug:
line 688 modified as follows:
Please check on lines 894 and 688 (not shown) for the issues mentioned
below.
Note that the ifs and {s in the following code snippet don't always follow
the kernel coding style, eg on line 901.
julia
-- Forwarded message --
Date: Sun, 16 Jul 2017 04:35:49 +0800
From: kbuild test
-- Forwarded message --
From: srishti sharma
Date: Thu, May 18, 2017 at 9:06 PM
Subject: Re: [PATCH] Staging: bcm2835-audio: bcm2835_ctl.c: Fixed a
comment coding style issue
To: Greg KH
On Thu, May 18, 2017 at 7:28 PM, Greg KH wrote:
> On Thu, May 18, 2017 at 04:20:15PM +0530,
The code under the error label may not be meaningful if error is reached
from line 495.
julia
-- Forwarded message --
Date: Sat, 29 Apr 2017 01:52:34 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: [staging:staging-testing 393/1005]
drivers/staging
As far as I can see, the only code that can be executed in line 621 - 635
is ret = rtw_resume_process(padapter);. Perhaps it can be simplified.
julia
-- Forwarded message --
Date: Fri, 28 Apr 2017 22:13:26 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject
Thanks Julia. I missed that and I'll fix it in my series.
Logan
On 14/04/17 09:19 AM, Julia Lawall wrote:
> It looks like &udev->cmdr_lock should be released at line 512 if it has
> not been released otherwise. The lock was taken at line 438.
>
> julia
>
> -- Forwarded message
It looks like &udev->cmdr_lock should be released at line 512 if it has
not been released otherwise. The lock was taken at line 438.
julia
-- Forwarded message --
Date: Fri, 14 Apr 2017 22:21:44 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: Re: [PATC
On Wed, 2017-03-01 at 11:25 +0100, Julia Lawall wrote:
> In both of the cited files (only one is shown), buffer is allocated
> using
> devm_kzalloc, so the kfree is not appropriate.
>
Thanks I'll get these fixed up.
Alan
___
devel mailing list
de...@l
In both of the cited files (only one is shown), buffer is allocated using
devm_kzalloc, so the kfree is not appropriate.
julia
-- Forwarded message --
Date: Wed, 1 Mar 2017 18:12:08 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: [staging:staging-testin
It looks like an unlock is missing before line 1797.
julia
-- Forwarded message --
Date: Wed, 15 Feb 2017 03:07:29 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: Re: [PATCH 2/3 staging-next] oom: Add notification for oom_score_adj
Hi Peter,
[auto bui
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Sun, Oct 02, 2016 at 10:
So my first patch is correct?
On Sun, Oct 2, 2016 at 9:39 PM, Greg KH wrote:
> On Sun, Oct 02, 2016 at 09:13:32PM +0530, Nadim Almas wrote:
>> sir i am new in linux kernel hacking so I just want to start with
>> something very simple ,so for sake of simplicity and learning I fixed
>> only one of
On Sun, Oct 02, 2016 at 09:13:32PM +0530, Nadim Almas wrote:
> sir i am new in linux kernel hacking so I just want to start with
> something very simple ,so for sake of simplicity and learning I fixed
> only one of these warning
That's great, but next time try to do a little bit more, just fixing
sir i am new in linux kernel hacking so I just want to start with
something very simple ,so for sake of simplicity and learning I fixed
only one of these warning
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/
> James,
> I’m pretty sure this port to upstream is flawed. See below
Yep. I missed that line. Thanks for review. Greg you can drop this one. I
will submit a updated version soon. This patch series is not
order dependent so the other patches are safe to land.
> On 5/9/16, 7:53 AM, "lustre-
Sorry for the mass forward, I was instructed to email more than just the
linux-wireless mailing list.
Any help would be appreciated.
Thanks!
-Andrew
Forwarded Message
Subject: Re: wilc1000 staging driver initialization failure
Date: Thu, 4 Feb 2016 13:26:04 -0500
On Fri, Sep 18, 2015 at 01:32:57PM +0100, Viacheslav Kovalevskyi wrote:
> On Thu, Sep 17, 2015 at 4:53 PM Greg KH wrote:
> >
> > On Thu, Sep 17, 2015 at 03:24:37PM +0100, Viacheslav Kovalevskyi wrote:
> > > Hi there,
> > >
> > > Apologies for the complete nuby question, I want to help with porting
On Thu, Sep 17, 2015 at 4:53 PM Greg KH wrote:
>
> On Thu, Sep 17, 2015 at 03:24:37PM +0100, Viacheslav Kovalevskyi wrote:
> > Hi there,
> >
> > Apologies for the complete nuby question, I want to help with porting
> > Android LMK (drivers/staging/android/lowmemorykiller.c) from the
> > staging to
On Thu, Sep 17, 2015 at 03:24:37PM +0100, Viacheslav Kovalevskyi wrote:
> Hi there,
>
> Apologies for the complete nuby question, I want to help with porting
> Android LMK (drivers/staging/android/lowmemorykiller.c) from the
> staging to the master. Where I can find more information about the
> cu
Hi there,
Apologies for the complete nuby question, I want to help with porting
Android LMK (drivers/staging/android/lowmemorykiller.c) from the
staging to the master. Where I can find more information about the
current challenges that need to be solved before porting it to the
master?
Or, maybe,
On Thu, Dec 11, 2014 at 07:43:15AM -0500, Kristopher Borer wrote:
> The kernel version is 3.13.0-32-generic
Ick, that's 68 thousand patches old (i.e. one year...)
Have you tried the 3.18 kernel release to see if it is better, because:
>
> Here is one example:
>
> BUG: unable to handle kernel N
The kernel version is 3.13.0-32-generic
Here is one example:
BUG: unable to handle kernel NULL pointer dereference at...
IP: [...] xhci_stream_id_to_ring+0x40/0x60
PGD 362a1067 PUD c9f49067 PMD 0
Oops: [#1] SMP
Modules linked in: elo_mt_input_mod(0F) eeepc_wmi ...
CPU: 1 PID: 20665 Comm: ...
On Wed, Dec 10, 2014 at 07:35:48PM -0500, Kristopher Borer wrote:
> Hello,
>
> I am looking to improve support for a USB board camera. It currently
> works fairly well, but we occasionally cause kernel panics while using
> OpenCV on Ubuntu 14.04.
What kernel version is that, and what is the oops
Hello,
I am looking to improve support for a USB board camera. It currently
works fairly well, but we occasionally cause kernel panics while using
OpenCV on Ubuntu 14.04.
Here is the device: e-consystems.com/5mp-usb-cameraboard.asp
We do not need an NDA. We can provide hardware, test scripts
On Thu, Aug 28, 2014 at 10:23:05AM +0800, Janet Liu wrote:
> On 08/28/2014 10:20 AM, Janet Liu wrote:
> >
> >
> >
> > Original Message
> >Subject: Re: [PATCH] staging:lustre:lnet: lib-md.c fix checkpath
> >warnings and errors.
> >Date: Tue, 26 Aug 2014 18:22:45 -0700
> >From: Greg
No worries. But Greg asked you to break the patch up into 4 patches:
patch 1: long lines
patch 2: spaces
patch 3: comments
patch 4: trailing statements.
Please resend.
regards,
dan carpenter
___
devel mailing list
de...@linuxdriverproject.org
http://
On 08/28/2014 10:20 AM, Janet Liu wrote:
Original Message
Subject: Re: [PATCH] staging:lustre:lnet: lib-md.c fix checkpath
warnings and errors.
Date: Tue, 26 Aug 2014 18:22:45 -0700
From: Greg KH
To: Janet Liu
CC: de...@driverdev.osuosl.org, linux-ker...@vger.kernel.org
On
On 21/06/14 21:24, Larry Finger wrote:
> On 06/21/2014 12:52 PM, Christian Lamparter wrote:
>> I think there's a reason why the development takes so long
>> (The RTL8192S* chips have been around since 2008, 2009)
>> and why we all have better things to do and write harsh
>> responses. As far as I c
On 21/06/14 20:52, Christian Lamparter wrote:
> On Saturday, June 21, 2014 06:45:07 PM Kristina Martšenko wrote:
>> On 20/06/14 23:52, Christian Lamparter wrote:
>>> rtl8192su development is chugging along. It just doesn't take place on
>>> driverdev list. The driver reached "feature parity" with r
On 06/21/2014 12:52 PM, Christian Lamparter wrote:
On Saturday, June 21, 2014 06:45:07 PM Kristina Martšenko wrote:
On 20/06/14 23:52, Christian Lamparter wrote:
On Friday, June 20, 2014 09:19:07 PM Xose Vazquez Perez wrote:
Kristina wrote:
I'm helping Greg do a bit of cleanup in the staging
On Saturday, June 21, 2014 06:45:07 PM Kristina Martšenko wrote:
> On 20/06/14 23:52, Christian Lamparter wrote:
> > On Friday, June 20, 2014 09:19:07 PM Xose Vazquez Perez wrote:
> >> Kristina wrote:
> >>
> >>> I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
> >>> nobody s
On 20/06/14 23:52, Christian Lamparter wrote:
> On Friday, June 20, 2014 09:19:07 PM Xose Vazquez Perez wrote:
>> Kristina wrote:
>>
>>> I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
>>> nobody seems to have worked towards moving rtl8712 out of staging in
>>> over a year.
On Friday, June 20, 2014 09:19:07 PM Xose Vazquez Perez wrote:
> Kristina wrote:
>
> > I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
> > nobody seems to have worked towards moving rtl8712 out of staging in
> > over a year. Are there any plans to clean it up and move it o
On Tue, Apr 15, 2014 at 01:17:42AM +0900, Masanari Iida wrote:
> Hi Maintainers,
>
> This patch did not pick up during 3.15-rc1 merge period.
> Please don't forget to pick up in 3.16.
> Regards,
>
> Masanari
>
> -- Forwarded message --
> From: suzuki
> Date: Fri, Feb 28, 2014 at
On Tue, Apr 15, 2014 at 01:17:42AM +0900, Masanari Iida wrote:
> Hi Maintainers,
>
> This patch did not pick up during 3.15-rc1 merge period.
That is because you didn't send it to the correct people :(
Always use the scripts/get_maintainer.pl tool, it will tell you the
correct addresses to use.
Hi Maintainers,
This patch did not pick up during 3.15-rc1 merge period.
Please don't forget to pick up in 3.16.
Regards,
Masanari
-- Forwarded message --
From: suzuki
Date: Fri, Feb 28, 2014 at 1:10 AM
Subject: [PATCH] [PATCH/RESENT] staging] speakup: fix typo in kobjects.c
To:
55 matches
Mail list logo
