public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: liao jaime <jaimeliao.tw@gmail.com>
Cc: linux-mtd@lists.infradead.org, tudor.ambarus@linaro.org,
	pratyush@kernel.org, miquel.raynal@bootlin.com,
	leoyu@mxic.com.tw, jaimeliao@mxic.com.tw
Subject: Re: [PATCH v2 1/1] mtd: spi-nor: sfdp: Get the 1-1-8 protocol from BFPT
Date: Thu, 14 Dec 2023 11:09:50 +0100	[thread overview]
Message-ID: <7eae51cda742c5e36d4a615a03bbe198@walle.cc> (raw)
In-Reply-To: <CAAQoYR=+gEwUuw-CbWio7-h9jAP4ESQshF_Ao=Q+pU5jhpejDg@mail.gmail.com>

>> > From: JaimeLiao <jaimeliao@mxic.com.tw>
>> >
>> > BFPT 17th DWORD contains the informations about 1-1-8,
>> > Parse BFPT 17 DWORD instruction to determine
>> > whether flash support 1-1-8, and set its dummy cycle
>> > accordingly.
>> >
>> > Signed-off-by: JaimeLiao <jaimeliao@mxic.com.tw>
>> 
>> Reviewed-by: Michael Walle <michael@walle.cc>
>> 
>> > ---
>> 
>> no need for a 0/N cover letter just for the changelog. That can
>> be included here below the "---".
>> 
>> And you can also keep my Rb tag.
> Got it.
> Would this version be accepted or should I send a new one?

No need for a new one. Just for your future patches.

-michael

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2023-12-14 10:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14  7:33 [PATCH v2 0/1] Get the 1-1-8 protocol from BFPT Jaime Liao
2023-12-14  7:33 ` [PATCH v2 1/1] mtd: spi-nor: sfdp: " Jaime Liao
2023-12-14  9:48   ` Michael Walle
2023-12-14 10:06     ` liao jaime
2023-12-14 10:09       ` Michael Walle [this message]
2023-12-14 10:11         ` liao jaime
2023-12-15  6:45   ` Tudor Ambarus
2023-12-15  6:59     ` liao jaime
2023-12-15  7:12       ` Tudor Ambarus
2023-12-15  7:27         ` liao jaime

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=7eae51cda742c5e36d4a615a03bbe198@walle.cc \
    --to=michael@walle.cc \
    --cc=jaimeliao.tw@gmail.com \
    --cc=jaimeliao@mxic.com.tw \
    --cc=leoyu@mxic.com.tw \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=pratyush@kernel.org \
    --cc=tudor.ambarus@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox