From: Greg KH <gregkh@linuxfoundation.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: akpm@linux-foundation.org, bp@suse.de, efault@gmx.de,
gorcunov@openvz.org, kirill.shutemov@linux.intel.com,
luto@amacapital.net, mingo@kernel.org, peterz@infradead.org,
tglx@linutronix.de, torvalds@linux-foundation.org,
stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "Revert "mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y"" has been added to the 4.14-stable tree
Date: Mon, 8 Jan 2018 11:09:05 +0100 [thread overview]
Message-ID: <20180108100905.GB18672@kroah.com> (raw)
In-Reply-To: <20180108100416.GA18672@kroah.com>
On Mon, Jan 08, 2018 at 11:04:16AM +0100, Greg KH wrote:
> On Mon, Jan 08, 2018 at 10:50:49AM +0100, Michal Hocko wrote:
> > On Mon 08-01-18 10:28:36, Greg KH wrote:
> > > On Mon, Jan 08, 2018 at 10:10:17AM +0100, gregkh@linuxfoundation.org wrote:
> > > >
> > > > This is a note to let you know that I've just added the patch titled
> > > >
> > > > Revert "mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y"
> > > >
> > > > to the 4.14-stable tree which can be found at:
> > > > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > > >
> > > > The filename of the patch is:
> > > > revert-mm-sparsemem-allocate-mem_section-at-runtime-for-config_sparsemem_extreme-y.patch
> > > > and it can be found in the queue-4.14 subdirectory.
> > > >
> > > > If you, or anyone else, feels it should not be added to the stable tree,
> > > > please let <stable@vger.kernel.org> know about it.
> > >
> > > Nope, broke the build, now dropped.
> >
> > Have you reverted both 7d7545295e714751fa236c6284167342b066d825
> > 4afaf6ea65acb07e151470580d89e6a2c0268610 (stable commits)?
>
> No, let me try that, I missed the second one...
No, I missed the first one. Ugh, it's been a long few months...
Anyway, that didn't work either, I'm just going to leave things alone
for now. If someone wants to send me a patch series of correct reverts,
I'll be glad to take them. But really, Linus's tree should just be
fixed, that will be an easier resolution here.
thanks,
greg k-h
prev parent reply other threads:[~2018-01-08 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 9:10 Patch "Revert "mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y"" has been added to the 4.14-stable tree gregkh
2018-01-08 9:28 ` Greg KH
2018-01-08 9:50 ` Michal Hocko
2018-01-08 10:04 ` Greg KH
2018-01-08 10:09 ` Greg KH [this message]
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=20180108100905.GB18672@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=efault@gmx.de \
--cc=gorcunov@openvz.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=luto@amacapital.net \
--cc=mhocko@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).