From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Guenter Roeck <linux@roeck-us.net>,
Sudip Mukherjee <sudip.mukherjee@sifive.com>
Cc: Tudor Ambarus <tudor.ambarus@microchip.com>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <michael@walle.cc>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
greentime.hu@sifive.com, jude.onyenegecha@sifive.com,
william.salmon@sifive.com, adnan.chowdhury@sifive.com,
ben.dooks@sifive.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] mtd: spi-nor: issi: is25wp256: Init flash based on SFDP
Date: Wed, 21 Dec 2022 10:49:46 +0200 [thread overview]
Message-ID: <84378cf6-c0ca-0cf4-c3f2-c65b40bc837d@linaro.org> (raw)
In-Reply-To: <96b4574d-8fe1-7662-5029-fc375f7b9ac9@linaro.org>
On 21.12.2022 09:03, Tudor Ambarus wrote:
> Would you please revert the patch locally and do the
> tests from below? Thanks!
Disregard this, I thought you have a real flash. Michael is right about
qemu.
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-12-21 8:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 18:48 [PATCH v3 1/2] mtd: spi-nor: issi: is25wp256: Init flash based on SFDP Sudip Mukherjee
2022-09-20 18:48 ` [PATCH v3 2/2] mtd: spi-nor: add SFDP fixups for Quad Page Program Sudip Mukherjee
2022-09-20 18:52 ` Sudip Mukherjee
2022-09-20 18:51 ` [PATCH v3 1/2] mtd: spi-nor: issi: is25wp256: Init flash based on SFDP Sudip Mukherjee
2022-09-22 14:19 ` Michael Walle
2022-09-23 18:31 ` Sudip Mukherjee
2022-11-22 10:26 ` Tudor Ambarus
2022-12-21 0:30 ` Guenter Roeck
2022-12-21 7:03 ` Tudor Ambarus
2022-12-21 8:49 ` Tudor Ambarus [this message]
2022-12-21 8:22 ` Michael Walle
2022-12-21 12:16 ` Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2022-09-20 18:47 Sudip Mukherjee
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=84378cf6-c0ca-0cf4-c3f2-c65b40bc837d@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=adnan.chowdhury@sifive.com \
--cc=ben.dooks@sifive.com \
--cc=greentime.hu@sifive.com \
--cc=jude.onyenegecha@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=sudip.mukherjee@sifive.com \
--cc=tudor.ambarus@microchip.com \
--cc=vigneshr@ti.com \
--cc=william.salmon@sifive.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