From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Reza Arbab <arbab@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] memory-hotplug: fix store_mem_state() return value
Date: Wed, 31 Aug 2016 17:01:05 +0200 [thread overview]
Message-ID: <20160831150105.GB26702@kroah.com> (raw)
In-Reply-To: <20160831143754.7trnlfaddyffhhtx@arbab-vm>
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@linuxfoundation.org> (supporter:DRIVER CORE, KOBJECTS, DEBUGFS, KERNFS AND SYSFS)
> linux-kernel@vger.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
next prev parent reply other threads:[~2016-08-31 15:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 19:07 [PATCH v2] memory-hotplug: fix store_mem_state() return value Reza Arbab
2016-05-26 14:43 ` Reza Arbab
2016-05-26 15:34 ` Greg Kroah-Hartman
2016-05-26 15:35 ` Greg Kroah-Hartman
2016-08-31 12:21 ` Greg Kroah-Hartman
2016-08-31 14:37 ` Reza Arbab
2016-08-31 15:01 ` Greg Kroah-Hartman [this message]
2016-08-31 15:44 ` [RESEND PATCH " Reza Arbab
2016-08-31 20:25 ` Andrew Morton
2016-08-31 21:06 ` David Rientjes
2016-08-31 23:38 ` Reza Arbab
2016-09-01 0:03 ` David Rientjes
2016-09-01 0:17 ` Reza Arbab
2016-09-01 0:28 ` David Rientjes
2016-09-01 1:57 ` Reza Arbab
2016-08-31 14:38 ` Reza Arbab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160831150105.GB26702@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arbab@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox