From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Amit Pundir <amit.pundir@linaro.org>
Cc: Boris Brezillon <boris.brezillon@free-electrons.com>,
alexander.levin@microsoft.com, han.xu@nxp.com,
marek.vasut@gmail.com, stable <stable@vger.kernel.org>,
stable-commits@vger.kernel.org
Subject: Re: Patch "mtd: nand: gpmi: Fix gpmi_nand_init() error path" has been added to the 4.4-stable tree
Date: Tue, 10 Apr 2018 23:16:59 +0200 [thread overview]
Message-ID: <20180410211659.GD19732@kroah.com> (raw)
In-Reply-To: <CAMi1Hd3NTzU=o8uU6=htakndEG6R4vG4y1dneCEh9HRt=QbwMg@mail.gmail.com>
On Wed, Apr 11, 2018 at 12:18:43AM +0530, Amit Pundir wrote:
> On 10 April 2018 at 14:34, <gregkh@linuxfoundation.org> wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > mtd: nand: gpmi: Fix gpmi_nand_init() error path
> >
> > to the 4.4-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:
> > mtd-nand-gpmi-fix-gpmi_nand_init-error-path.patch
> > and it can be found in the queue-4.4 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.
> >
>
> This patch broke ARM builds at kernelci
> https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.127-170-g7914585b83e0/
>
> It depends on nand_cleanup() introduced in d44154f969a4 ("mtd: nand:
> Provide nand_cleanup() function to free NAND related resources")
Thanks, now dropped.
greg k-h
prev parent reply other threads:[~2018-04-10 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 9:04 Patch "mtd: nand: gpmi: Fix gpmi_nand_init() error path" has been added to the 4.4-stable tree gregkh
2018-04-10 18:48 ` Amit Pundir
2018-04-10 21:16 ` 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=20180410211659.GD19732@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.levin@microsoft.com \
--cc=amit.pundir@linaro.org \
--cc=boris.brezillon@free-electrons.com \
--cc=han.xu@nxp.com \
--cc=marek.vasut@gmail.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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 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.