All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tokunori Ikegami <ikegami@allied-telesis.co.jp>
Cc: Chris Packham <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, 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 08:19:29 +0200	[thread overview]
Message-ID: <20180702061929.GA7611@kroah.com> (raw)
In-Reply-To: <20180702025045.29896-2-ikegami@allied-telesis.co.jp>

On Mon, Jul 02, 2018 at 11:50:42AM +0900, Tokunori Ikegami wrote:
> For the word write it is checked if the chip has the correct value.
> But it is not checked for the write buffer as only checked if ready.
> To make sure for the write buffer change to check the value.
> 
> It is enough as this patch is only checking the last written word.
> Since it is described by data sheets to check the operation status.
> 
> Signed-off-by: Tokunori Ikegami <ikegami@allied-telesis.co.jp>
> Reviewed-by: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
> Cc: Chris Packham <chris.packham@alliedtelesis.co.nz>
> Cc: Brian Norris <computersforpeace@gmail.com>
> Cc: David Woodhouse <dwmw2@infradead.org>
> Cc: Boris Brezillon <boris.brezillon@free-electrons.com>
> Cc: Marek Vasut <marek.vasut@gmail.com>
> Cc: Richard Weinberger <richard@nod.at>
> Cc: Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>
> Cc: linux-mtd@lists.infradead.org
> Cc: stable@vger.kernel.org
> Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
> ---
>  drivers/mtd/chips/cfi_cmdset_0002.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

What are the git commit ids for all of these patches, and what stable
tree do they need to go to?

thanks,

greg k-h

  reply	other threads:[~2018-07-02  6:19 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 [this message]
2018-07-02  7:16     ` IKEGAMI Tokunori
2018-07-02  7:23       ` Greg Kroah-Hartman
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=20180702061929.GA7611@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.