lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Mon, 12 Mar 2018 16:10:59 +0200
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Sudip Mukherjee <sudipm.mukherjee@...il.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 01/12] parport: ax88796: Delete an error message for a
 failed memory allocation in parport_ax88796_probe()

On Sat, Mar 3, 2018 at 11:00 PM, Sudip Mukherjee
<sudipm.mukherjee@...il.com> wrote:
> Hi Greg,
>
> On Thu, Mar 01, 2018 at 01:06:09PM +0100, Greg Kroah-Hartman wrote:
>> On Thu, Mar 01, 2018 at 12:46:07PM +0200, Andy Shevchenko wrote:
>> > On Wed, Feb 7, 2018 at 9:47 PM, Sudip Mukherjee
>> > <sudipm.mukherjee@...il.com> wrote:
>> > > From: Markus Elfring <elfring@...rs.sourceforge.net>
>> > >
>> > > Omit an extra message for a memory allocation failure in this function.
>> > >
>> > > This issue was detected by using the Coccinelle software.
>> > >
>> >
>> > Greg, just to be sure this series is under your scope.
>> > IIRC it had been sent during merge window, though it looks like your
>> > tty tree doesn't include it yet, while even older patches, which were
>> > sent as well during merge window, made it
>>
>> It's in my large "to-review" queue...
>>
>> Personally, stuff like this, from this specific developer, ends up at
>> the bottom of that list as well...
>
> do you want me to reorganize the series and resend?
> I can send patches 1 - 3 later.

Greg, this series contains patches from two developers, the patches
starting from #4 is more important since they are enabling BrainBox
multi I/O cards while cleaning up the partport_serial driver itself.
I understand you have a long queue, but would we have a chance to get
into v4.17 with these?

-- 
With Best Regards,
Andy Shevchenko

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ