From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> To: Laurent Dufour <ldufour@linux.ibm.com> Cc: akpm@linux-foundation.org, David Hildenbrand <david@redhat.com>, Oscar Salvador <osalvador@suse.de>, mhocko@suse.com, linux-mm@kvack.org, "Rafael J . Wysocki" <rafael@kernel.org>, nathanl@linux.ibm.com, cheloha@linux.ibm.com, Tony Luck <tony.luck@intel.com>, Fenghua Yu <fenghua.yu@intel.com>, linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH v3 1/3] mm: replace memmap_context by meminit_context Date: Wed, 16 Sep 2020 09:40:47 +0200 [thread overview] Message-ID: <20200916074047.GA189144@kroah.com> (raw) In-Reply-To: <0b3f2eb1-0efa-a491-c509-d16a7e18d8e8@linux.ibm.com> On Wed, Sep 16, 2020 at 09:29:22AM +0200, Laurent Dufour wrote: > Le 16/09/2020 à 08:33, Greg Kroah-Hartman a écrit : > > On Tue, Sep 15, 2020 at 03:26:24PM +0200, Laurent Dufour wrote: > > > The memmap_context enum is used to detect whether a memory operation is due > > > to a hot-add operation or happening at boot time. > > > > > > Make it general to the hotplug operation and rename it as meminit_context. > > > > > > There is no functional change introduced by this patch > > > > > > Suggested-by: David Hildenbrand <david@redhat.com> > > > Signed-off-by: Laurent Dufour <ldufour@linux.ibm.com> > > > --- > > > arch/ia64/mm/init.c | 6 +++--- > > > include/linux/mm.h | 2 +- > > > include/linux/mmzone.h | 11 ++++++++--- > > > mm/memory_hotplug.c | 2 +- > > > mm/page_alloc.c | 10 +++++----- > > > 5 files changed, 18 insertions(+), 13 deletions(-) > > > > <formletter> > > > > This is not the correct way to submit patches for inclusion in the > > stable kernel tree. Please read: > > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html > > for how to do this properly. > > > > </formletter> > > Hi Greg, > > I'm sorry, I read that document few days ago before sending the series and > again this morning, but I can't figure out what I missed (following option > 1). > > Should the "Cc: stable@vger.kernel.org" tag be on each patch of the series > even if the whole series has been sent to stable ? That should be on any patch you expect to show up in a stable kernel release. > Should the whole series sent again (v4) instead of sending a fix as a reply to ? It's up to the maintainer what they want, but as it is, this patch is not going to end up in stable kernel release (which it looks like is the right thing to do...) thanks, greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> To: Laurent Dufour <ldufour@linux.ibm.com> Cc: akpm@linux-foundation.org, David Hildenbrand <david@redhat.com>, Oscar Salvador <osalvador@suse.de>, mhocko@suse.com, linux-mm@kvack.org, "Rafael J . Wysocki" <rafael@kernel.org>, nathanl@linux.ibm.com, cheloha@linux.ibm.com, Tony Luck <tony.luck@intel.com>, Fenghua Yu <fenghua.yu@intel.com>, linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH v3 1/3] mm: replace memmap_context by meminit_context Date: Wed, 16 Sep 2020 07:40:47 +0000 [thread overview] Message-ID: <20200916074047.GA189144@kroah.com> (raw) In-Reply-To: <0b3f2eb1-0efa-a491-c509-d16a7e18d8e8@linux.ibm.com> On Wed, Sep 16, 2020 at 09:29:22AM +0200, Laurent Dufour wrote: > Le 16/09/2020 à 08:33, Greg Kroah-Hartman a écrit : > > On Tue, Sep 15, 2020 at 03:26:24PM +0200, Laurent Dufour wrote: > > > The memmap_context enum is used to detect whether a memory operation is due > > > to a hot-add operation or happening at boot time. > > > > > > Make it general to the hotplug operation and rename it as meminit_context. > > > > > > There is no functional change introduced by this patch > > > > > > Suggested-by: David Hildenbrand <david@redhat.com> > > > Signed-off-by: Laurent Dufour <ldufour@linux.ibm.com> > > > --- > > > arch/ia64/mm/init.c | 6 +++--- > > > include/linux/mm.h | 2 +- > > > include/linux/mmzone.h | 11 ++++++++--- > > > mm/memory_hotplug.c | 2 +- > > > mm/page_alloc.c | 10 +++++----- > > > 5 files changed, 18 insertions(+), 13 deletions(-) > > > > <formletter> > > > > This is not the correct way to submit patches for inclusion in the > > stable kernel tree. Please read: > > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html > > for how to do this properly. > > > > </formletter> > > Hi Greg, > > I'm sorry, I read that document few days ago before sending the series and > again this morning, but I can't figure out what I missed (following option > 1). > > Should the "Cc: stable@vger.kernel.org" tag be on each patch of the series > even if the whole series has been sent to stable ? That should be on any patch you expect to show up in a stable kernel release. > Should the whole series sent again (v4) instead of sending a fix as a reply to ? It's up to the maintainer what they want, but as it is, this patch is not going to end up in stable kernel release (which it looks like is the right thing to do...) thanks, greg k-h
next prev parent reply other threads:[~2020-09-16 7:40 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-15 9:41 [PATCH v3 0/3] mm: fix memory to node bad links in sysfs Laurent Dufour 2020-09-15 9:41 ` Laurent Dufour 2020-09-15 9:41 ` [PATCH v3 1/3] mm: replace memmap_context by memplug_context Laurent Dufour 2020-09-15 9:41 ` Laurent Dufour 2020-09-15 10:17 ` David Hildenbrand 2020-09-15 10:17 ` David Hildenbrand 2020-09-15 10:28 ` Oscar Salvador 2020-09-15 10:28 ` Oscar Salvador 2020-09-15 12:15 ` Michal Hocko 2020-09-15 12:15 ` Michal Hocko 2020-09-15 13:26 ` [PATCH v3 1/3] mm: replace memmap_context by meminit_context Laurent Dufour 2020-09-15 13:26 ` Laurent Dufour 2020-09-15 13:35 ` Michal Hocko 2020-09-15 13:35 ` Michal Hocko 2020-09-16 6:33 ` Greg Kroah-Hartman 2020-09-16 6:33 ` Greg Kroah-Hartman 2020-09-16 7:29 ` Laurent Dufour 2020-09-16 7:29 ` Laurent Dufour 2020-09-16 7:40 ` Greg Kroah-Hartman [this message] 2020-09-16 7:40 ` Greg Kroah-Hartman 2020-09-16 7:47 ` Laurent Dufour 2020-09-16 7:47 ` Laurent Dufour 2020-09-16 7:52 ` David Hildenbrand 2020-09-16 7:52 ` David Hildenbrand 2020-09-16 16:09 ` Laurent Dufour 2020-09-16 16:09 ` Laurent Dufour 2020-09-16 23:37 ` Andrew Morton 2020-09-16 23:37 ` Andrew Morton 2020-09-17 8:00 ` Laurent Dufour 2020-09-17 8:00 ` Laurent Dufour 2020-09-15 9:41 ` [PATCH v3 2/3] mm: don't rely on system state to detect hot-plug operations Laurent Dufour 2020-09-15 9:41 ` Laurent Dufour 2020-09-15 10:31 ` Oscar Salvador 2020-09-15 10:31 ` Oscar Salvador 2020-09-15 12:19 ` Michal Hocko 2020-09-15 12:19 ` Michal Hocko 2020-09-15 9:41 ` [PATCH v3 3/3] mm: don't panic when links can't be created in sysfs Laurent Dufour 2020-09-15 9:41 ` Laurent Dufour 2020-09-15 10:33 ` Oscar Salvador 2020-09-15 10:33 ` Oscar Salvador
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=20200916074047.GA189144@kroah.com \ --to=gregkh@linuxfoundation.org \ --cc=akpm@linux-foundation.org \ --cc=cheloha@linux.ibm.com \ --cc=david@redhat.com \ --cc=fenghua.yu@intel.com \ --cc=ldufour@linux.ibm.com \ --cc=linux-ia64@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mhocko@suse.com \ --cc=nathanl@linux.ibm.com \ --cc=osalvador@suse.de \ --cc=rafael@kernel.org \ --cc=stable@vger.kernel.org \ --cc=tony.luck@intel.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.