linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Thiery <heiko.thiery@gmail.com>
To: Michael Walle <michael@walle.cc>
Cc: Pratyush Yadav <p.yadav@ti.com>,
	linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
	Tudor Ambarus <tudor.ambarus@microchip.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH v2 1/2] mtd: spi-nor: sfdp: save a copy of the SFDP data
Date: Tue, 23 Mar 2021 20:03:18 +0100	[thread overview]
Message-ID: <CAEyMn7bt6iYVBUOoJGs1a2VA-AWf7AyCJ0MJXN9NzQsOuVaQqA@mail.gmail.com> (raw)
In-Reply-To: <C88FBBF6-4F5C-43A1-951E-332AEE9E3B3A@walle.cc>

Hi Michael,

Am Di., 23. März 2021 um 19:45 Uhr schrieb Michael Walle <michael@walle.cc>:
>
> Am 23. März 2021 18:37:17 MEZ schrieb Pratyush Yadav <p.yadav@ti.com>:
> >On 23/03/21 03:31PM, Michael Walle wrote:
> >> Due to possible mode switching to 8D-8D-8D, it might not be possible
> >to
> >> read the SFDP after the initial probe. To be able to dump the SFDP
> >via
> >> sysfs afterwards, make a complete copy of it.
> >>
> >> Signed-off-by: Michael Walle <michael@walle.cc>
> >
> >Reviewed-by: Pratyush Yadav <p.yadav@ti.com>

Tested-by: Heiko Thiery <heiko.thiery@gmail.com>

>
> thanks for reviewing!
>
> -michael
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2021-03-23 19:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 14:31 [PATCH v2 0/2] mtd: spi-nor: support dumping sfdp tables Michael Walle
2021-03-23 14:31 ` [PATCH v2 1/2] mtd: spi-nor: sfdp: save a copy of the SFDP data Michael Walle
2021-03-23 17:37   ` Pratyush Yadav
2021-03-23 18:43     ` Michael Walle
2021-03-23 19:03       ` Heiko Thiery [this message]
2021-03-23 14:31 ` [PATCH v2 2/2] mtd: spi-nor: add initial sysfs support Michael Walle
2021-03-23 17:40   ` Pratyush Yadav
2021-03-23 19:04   ` Heiko Thiery

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=CAEyMn7bt6iYVBUOoJGs1a2VA-AWf7AyCJ0MJXN9NzQsOuVaQqA@mail.gmail.com \
    --to=heiko.thiery@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael@walle.cc \
    --cc=miquel.raynal@bootlin.com \
    --cc=p.yadav@ti.com \
    --cc=richard@nod.at \
    --cc=tudor.ambarus@microchip.com \
    --cc=vigneshr@ti.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).