All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: IKEGAMI Tokunori <ikegami@allied-telesis.co.jp>
Cc: PACKHAM Chris <chris.packham@alliedtelesis.co.nz>,
	Brian Norris <computersforpeace@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Boris Brezillon <boris.brezillon@free-electrons.com>,
	Marek Vasut <marek.vasut@gmail.com>,
	Richard Weinberger <richard@nod.at>,
	Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Boris Brezillon <boris.brezillon@bootlin.com>
Subject: Re: [PATCH 1/4] mtd: cfi_cmdset_0002: Change write buffer to check correct value
Date: Mon, 2 Jul 2018 09:23:11 +0200	[thread overview]
Message-ID: <20180702072311.GA4817@kroah.com> (raw)
In-Reply-To: <TY1PR01MB095431D99EEBB4D53459354BDC430@TY1PR01MB0954.jpnprd01.prod.outlook.com>

On Mon, Jul 02, 2018 at 07:16:47AM +0000, IKEGAMI Tokunori wrote:
> Hi Greg-san,
> 
> The commit IDs on mainline are below.
> 
>   1. dfeae1073583 mtd: cfi_cmdset_0002: Change write buffer to check correct value
>   2. 85a82e28b023 mtd: cfi_cmdset_0002: Change definition naming to retry write operation
>   3. 45f75b8a919a mtd: cfi_cmdset_0002: Change erase functions to retry for error
>   4. 79ca484b6130 mtd: cfi_cmdset_0002: Change erase functions to check chip good only
> 
> Note:
>   The patches just sent today as revised are only existing with commit IDs on my local environment.
>   Also the patches are existing on the Linux MTD development patchwork as below but the commit IDs are not assigned.
>     <https://patchwork.ozlabs.org/project/linux-mtd/list/?series=53133>
> 
>   If those revised patches should be applied anywhere to have commit IDs at first please let me know.
>   Probably it should be consulted with the MTD maintainer Boris-san.

And what stable tree(s) do you want to see these applied to?

thanks,

greg k-h

  reply	other threads:[~2018-07-02  7:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180702025045.29896-1-ikegami@allied-telesis.co.jp>
2018-07-02  2:50 ` [PATCH 1/4] mtd: cfi_cmdset_0002: Change write buffer to check correct value Tokunori Ikegami
2018-07-02  6:19   ` Greg Kroah-Hartman
2018-07-02  7:16     ` IKEGAMI Tokunori
2018-07-02  7:23       ` Greg Kroah-Hartman [this message]
2018-07-02  7:34         ` IKEGAMI Tokunori
2018-07-06 10:11         ` IKEGAMI Tokunori
2018-07-10 14:45           ` Greg Kroah-Hartman
2018-07-10 23:20             ` IKEGAMI Tokunori
2018-07-02  2:50 ` [PATCH 2/4] mtd: cfi_cmdset_0002: Change definition naming to retry write operation Tokunori Ikegami
2018-07-02  2:50 ` [PATCH 3/4] mtd: cfi_cmdset_0002: Change erase functions to retry for error Tokunori Ikegami
2018-07-02  2:50 ` [PATCH 4/4] mtd: cfi_cmdset_0002: Change erase functions to check chip good only Tokunori Ikegami

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=20180702072311.GA4817@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=boris.brezillon@bootlin.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=ikegami@allied-telesis.co.jp \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=richard@nod.at \
    --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.