linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>
Cc: Boris Brezillon <boris.brezillon@free-electrons.com>,
	Cyrille Pitchen <cyrille.pitchen@atmel.com>,
	marek.vasut@gmail.com, linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org, richard@nod.at
Subject: Re: [PATCH 1/1] mtd: spi-nor: remove WARN_ONCE() message in spi_nor_write()
Date: Wed, 8 Feb 2017 18:23:47 -0800	[thread overview]
Message-ID: <20170209022347.GO94627@google.com> (raw)
In-Reply-To: <4ffbad4b-f1a5-a998-fe5b-f73b934435e4@wedev4u.fr>

On Tue, Dec 13, 2016 at 05:43:52PM +0100, Cyrille Pitchen wrote:
> Le 08/12/2016 à 16:31, Boris Brezillon a écrit :
> > On Tue, 6 Dec 2016 18:14:24 +0100
> > Cyrille Pitchen <cyrille.pitchen@atmel.com> wrote:
> > 
> >> This patch removes the WARN_ONCE() test in spi_nor_write().
> >> This macro triggers the display of a warning message almost every time we
> >> use a UBI file-system because a write operation is performed at offset 64,
> >> which is in the middle of the SPI NOR memory page. This is a valid
> >> operation for ubifs.
> >>
> >> Hence this warning is pretty annoying and useless so we just remove it.
> >>
> >> Signed-off-by: Cyrille Pitchen <cyrille.pitchen@atmel.com>
> >> Suggested-by: Richard Weinberger <richard@nod.at>
> >> Suggested-by: Andras Szemzo <szemzo.andras@gmail.com>
> > 
> > Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> > 
> Applied to git://github.com/spi-nor/linux.git

Do you have any idea on how to handle or communicate this better? I
recall Michal added this because he was adding new write looping that
didn't previously exist; we might create partial-page writes because his
SPI controller was too dumb to make larger ones.

Anyway, since this is hitting real (and more or less false positive)
use cases, then this patch is probably good.

Brian

  reply	other threads:[~2017-02-09  2:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-06 17:14 [PATCH 1/1] mtd: spi-nor: remove WARN_ONCE() message in spi_nor_write() Cyrille Pitchen
2016-12-06 19:00 ` Marek Vasut
2016-12-06 23:38   ` Cyrille Pitchen
2016-12-07  3:07     ` Marek Vasut
2016-12-07  6:21       ` Krzeminski, Marcin (Nokia - PL/Wroclaw)
2016-12-07 13:07         ` Cyrille Pitchen
2016-12-07 13:50           ` Krzeminski, Marcin (Nokia - PL/Wroclaw)
2016-12-07  7:40       ` Boris Brezillon
2016-12-08 15:31 ` Boris Brezillon
2016-12-13 16:43   ` Cyrille Pitchen
2017-02-09  2:23     ` Brian Norris [this message]
2017-02-09 13:50       ` Cyrille Pitchen
2017-02-10 18:29         ` Brian Norris

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=20170209022347.GO94627@google.com \
    --to=computersforpeace@gmail.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=cyrille.pitchen@atmel.com \
    --cc=cyrille.pitchen@wedev4u.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=richard@nod.at \
    /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).