From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Joakim.Tjernlund@infinera.com,
boris.brezillon@free-electrons.com,
chris.packham@alliedtelesis.co.nz, computersforpeace@gmail.com,
cyrille.pitchen@wedev4u.fr, dwmw2@infradead.org,
ikegami@allied-telesis.co.jp, linux-mtd@lists.infradead.org,
marek.vasut@gmail.com, richard@nod.at,
stable-commits@vger.kernel.org
Subject: Re: Patch "mtd: cfi_cmdset_0002: Change erase functions to retry for error" has been added to the 4.17-stable tree
Date: Sun, 1 Jul 2018 15:34:03 +0200 [thread overview]
Message-ID: <20180701153403.6ea52135@bbrezillon> (raw)
In-Reply-To: <20180701102205.GA30410@kroah.com>
Hi Greg,
On Sun, 1 Jul 2018 12:22:05 +0200
Greg KH <gregkh@linuxfoundation.org> wrote:
> On Sun, Jul 01, 2018 at 12:09:21PM +0200, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > mtd: cfi_cmdset_0002: Change erase functions to retry for error
> >
> > to the 4.17-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> Nope, this broke the build everywhere, so I've dropped it from all trees
> now. If you want this backported, please provide a working version.
That's not surprising, this patch depends on "mtd: cfi_cmdset_0002:
Change definition naming to retry write" which did not apply cleanly on
4.17.
To be honest, I was not convinced those 2 patches deserved to be
backported to stable releases, but Joakim and Ikegami thought they were
good candidate. I'll let Ikegami propose a revised version of those 2
patches that apply cleanly on 4.17 if he wants.
Sorry for the inconvenience.
Regards,
Boris
next prev parent reply other threads:[~2018-07-01 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 10:09 Patch "mtd: cfi_cmdset_0002: Change erase functions to retry for error" has been added to the 4.17-stable tree gregkh
2018-07-01 10:22 ` Greg KH
2018-07-01 13:34 ` Boris Brezillon [this message]
2018-07-02 2:58 ` IKEGAMI Tokunori
-- strict thread matches above, loose matches on Subject: below --
2018-07-10 14:51 gregkh
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=20180701153403.6ea52135@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=Joakim.Tjernlund@infinera.com \
--cc=boris.brezillon@free-electrons.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=ikegami@allied-telesis.co.jp \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=stable-commits@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.