From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nicolas Boichat <drinkcat@chromium.org>
Cc: Sasha Levin <sashal@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Levin Alexander <Alexander.Levin@microsoft.com>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>, Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Michal Hocko <mhocko@suse.com>,
Mel Gorman <mgorman@techsingularity.net>,
Huaisheng Ye <yehs1@lenovo.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Yong Wu <yong.wu@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Tomasz Figa <tfiga@google.com>,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
Christoph Hellwig <hch@infradead.org>,
Matthew Wilcox <willy@infradead.org>,
Hsin-Yi Wang <hsinyi@chromium.org>,
stable@vger.kernel.org
Subject: Re: [patch 08/22] mm: add support for kmem caches in DMA32 zone
Date: Sun, 31 Mar 2019 16:54:56 +0200 [thread overview]
Message-ID: <20190331145456.GA675@kroah.com> (raw)
In-Reply-To: <CANMq1KBDFTBFV-AsS2czSQ3A_q1KHLW7bD_T2RVoaE3ob5gtxQ@mail.gmail.com>
On Sun, Mar 31, 2019 at 07:45:05PM +0800, Nicolas Boichat wrote:
> Hi Sasha,
>
> On Sat, Mar 30, 2019 at 9:45 PM Sasha Levin <sashal@kernel.org> wrote:
> >
> > Hi,
> >
> > [This is an automated email]
> >
> > This commit has been processed because it contains a -stable tag.
> > The stable tag indicates that it's relevant for the following trees: all
> >
> > The bot has tested the following trees: v5.0.5, v4.19.32, v4.14.109, v4.9.166, v4.4.177, v3.18.137.
> >
> > v5.0.5: Build OK!
> > v4.19.32: Build OK!
> > v4.14.109: Failed to apply! Possible dependencies:...
> > v4.9.166: Failed to apply! Possible dependencies:...
> > v4.4.177: Failed to apply! Possible dependencies:...
> > v3.18.137: Failed to apply! Possible dependencies:...
> >
> > How should we proceed with this patch?
>
> As highlighted in the stable notes for the series, the regression
> happened in 4.15, sounds like I should have added some `# 4.15.x`
> after the stable cc?
>
> So we are ok with having the series applied to 4.19 and 5.0 only.
That is fine, thanks!
greg k-h
prev parent reply other threads:[~2019-03-31 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 3:43 [patch 08/22] mm: add support for kmem caches in DMA32 zone akpm
2019-03-29 14:15 ` Christopher Lameter
2019-03-29 15:04 ` Nicolas Boichat
[not found] ` <20190330134526.281B6218AE@mail.kernel.org>
2019-03-31 11:45 ` Nicolas Boichat
2019-03-31 14:54 ` Greg Kroah-Hartman [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=20190331145456.GA675@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Alexander.Levin@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=drinkcat@chromium.org \
--cc=hch@infradead.org \
--cc=hsinyi@chromium.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=joro@8bytes.org \
--cc=matthias.bgg@gmail.com \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=robin.murphy@arm.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tfiga@google.com \
--cc=willy@infradead.org \
--cc=yehs1@lenovo.com \
--cc=yingjoe.chen@mediatek.com \
--cc=yong.wu@mediatek.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: 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).