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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160831150105.GB26702@kroah.com>
Date:   Wed, 31 Aug 2016 17:01:05 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Reza Arbab <arbab@...ux.vnet.ibm.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] memory-hotplug: fix store_mem_state() return value

On Wed, Aug 31, 2016 at 09:37:55AM -0500, Reza Arbab wrote:
> On Wed, Aug 31, 2016 at 02:21:28PM +0200, Greg Kroah-Hartman wrote:
> > > I can't find where this might have been committed. Am I being
> > > impatient, or did it slip through the cracks?
> > 
> > I think it fell through, can you resend it and cc: all of the people
> > involved in this subsystem, like you did for your other patch series?
> 
> I can resend, but I'm not sure what you mean by the rest--this was a
> singleton patch, and you're the only one listed by get_maintainer.pl:
> 
> $ scripts/get_maintainer.pl drivers/base/memory.c
> Greg Kroah-Hartman <gregkh@...uxfoundation.org> (supporter:DRIVER CORE, KOBJECTS, DEBUGFS, KERNFS AND SYSFS)
> linux-kernel@...r.kernel.org (open list)

You sent in other memory-hotplug patches that got merged through the -mm
tree. I suggest doing that here as well, as those developers know this
code much better than I do.

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ