linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: masonccyang@mxic.com.tw
Cc: "Boris Brezillon" <boris.brezillon@collabora.com>,
	allison@lohutok.net, bbrezillon@kernel.org,
	frieder.schrempf@kontron.de, juliensu@mxic.com.tw,
	linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
	rfontana@redhat.com, richard@nod.at, s.hauer@pengutronix.de,
	stefan@agner.ch, tglx@linutronix.de, vigneshr@ti.com,
	yuehaibing@huawei.com
Subject: Re: [PATCH v3 1/4] mtd: rawnand: Add support manufacturer specific lock/unlock operation
Date: Wed, 11 Mar 2020 08:25:22 +0100	[thread overview]
Message-ID: <20200311082522.53313163@xps13> (raw)
In-Reply-To: <OFCDE22522.001A7410-ON48258528.000E260F-48258528.000EA7E7@mxic.com.tw>

Hi Mason, Boris,

masonccyang@mxic.com.tw wrote on Wed, 11 Mar 2020 10:40:04 +0800:

> Hi Boris,
> 
> > > Add nand_lock() & nand_unlock() for manufacturer specific lock &   
> unlock
> > > operation while the device supports Block Portection function.
> > > 
> > > Signed-off-by: Mason Yang <masonccyang@mxic.com.tw>
> > > Reported-by: kbuild test robot <lkp@intel.com>  
> > 
> > Reported-by on something that's not a fix doesn't make sense. I know
> > the 0day bot asked you to add this tag, but that should only be done if
> > you submit a separate patch, ideally with a Fixes tag. If the offending
> > patch has not been merged yet, you should just fix the commit and ignore
> > the Reported-by tag (you can mention who reported the problem in the
> > changelog though).

Yesterday when applying all the NAND patches my personal IP address got
flagged as spam by mistake (~500 mails in ~10s) so I could not answer
manually as I wished.

Indeed, this Reported-by tag was not needed and I dropped it manually
when applying. This tag is meant to show an error that was existing
*before* your series and that you are fixing with your series. This is
not something you should add when a robot tells you something is wrong
in your series.

Also, I rewrote several paragraphs and I prefixed two of them with "mtd:
rawnand: macronix:".

Thanks,
Miquèl

  reply	other threads:[~2020-03-11  7:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03  7:21 [PATCH v3 0/4] mtd: rawnand: Add support Macronix Block Portection & Deep Power Down mode Mason Yang
2020-03-03  7:21 ` [PATCH v3 1/4] mtd: rawnand: Add support manufacturer specific lock/unlock operation Mason Yang
2020-03-10 18:30   ` Miquel Raynal
2020-03-10 19:27   ` Boris Brezillon
2020-03-11  2:40     ` masonccyang
2020-03-11  7:25       ` Miquel Raynal [this message]
2020-03-03  7:21 ` [PATCH v3 2/4] mtd: rawnand: Add support Macronix Block Protection function Mason Yang
2020-03-03  7:21 ` [PATCH v3 3/4] mtd: rawnand: Add support manufacturer specific suspend/resume operation Mason Yang
2020-03-10 18:30   ` Miquel Raynal
2020-03-10 19:33   ` Boris Brezillon
2020-03-11  5:40     ` masonccyang
2020-03-11  7:43       ` Miquel Raynal
2020-03-11  7:56         ` Boris Brezillon
2020-03-12  1:45         ` masonccyang
2020-03-10 19:39   ` Boris Brezillon
2020-03-10 19:41     ` Boris Brezillon
2020-03-11  6:13       ` masonccyang
2020-03-11  8:01         ` Boris Brezillon
2020-03-12  1:48           ` masonccyang
2020-03-03  7:21 ` [PATCH v3 4/4] mtd: rawnand: Add support Macronix deep power down mode Mason Yang
2020-03-09 13:14 ` [PATCH v3 0/4] mtd: rawnand: Add support Macronix Block Portection & Deep Power Down mode Miquel Raynal
2020-03-10  2:30   ` masonccyang
2020-03-10  7:44     ` Miquel Raynal

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=20200311082522.53313163@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=allison@lohutok.net \
    --cc=bbrezillon@kernel.org \
    --cc=boris.brezillon@collabora.com \
    --cc=frieder.schrempf@kontron.de \
    --cc=juliensu@mxic.com.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=masonccyang@mxic.com.tw \
    --cc=rfontana@redhat.com \
    --cc=richard@nod.at \
    --cc=s.hauer@pengutronix.de \
    --cc=stefan@agner.ch \
    --cc=tglx@linutronix.de \
    --cc=vigneshr@ti.com \
    --cc=yuehaibing@huawei.com \
    /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).