From: Michael Walle <michael@walle.cc>
To: Pratyush Yadav <me@yadavpratyush.com>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Richard Weinberger <richard@nod.at>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Jungseung Lee <js07.lee@samsung.com>
Subject: Re: [PATCH v2 1/4] mtd: spi-nor: cleanup common code
Date: Mon, 14 Sep 2020 13:09:33 +0200 [thread overview]
Message-ID: <6d52e1bdbbefc9383904e28bcc1c78a7@walle.cc> (raw)
In-Reply-To: <20200914094046.tccoc54n7e36zzyr@yadavpratyush.com>
Hi Pratyush,
Am 2020-09-14 11:40, schrieb Pratyush Yadav:
> Hi Michael,
>
> *sigh* This patch will cause a _lot_ of conflicts with my series [0].
> It
> should hopefully go in the next merge window so maybe you can rebase on
> top of it? Dunno.
Could you pick up this patch in some form in your series? It looks like
your
series touches most/some of the functions. The patch just removes code
repetitions.
TBH I don't need this patch as I just can implement my new one-byte
command
using the current "if (nor->spimem) {} else {}" pattern.
-michael
next prev parent reply other threads:[~2020-09-14 11:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 22:26 [PATCH v2 0/4] mtd: spi-nor: OTP support Michael Walle
2020-09-11 22:26 ` [PATCH v2 1/4] mtd: spi-nor: cleanup common code Michael Walle
2020-09-14 9:40 ` Pratyush Yadav
2020-09-14 11:09 ` Michael Walle [this message]
2020-09-14 14:50 ` Pratyush Yadav
2020-09-11 22:26 ` [PATCH v2 2/4] mtd: spi-nor: add OTP support Michael Walle
2020-10-01 5:34 ` Heiko Thiery
2020-09-11 22:26 ` [PATCH v2 3/4] mtd: spi-nor: implement OTP support for Macronix and similar flashes Michael Walle
2020-10-01 5:35 ` Heiko Thiery
2020-09-11 22:26 ` [PATCH v2 4/4] mtd: spi-nor: implement OTP support for Winbond " Michael Walle
2020-10-01 5:35 ` Heiko Thiery
2020-09-14 11:24 ` [PATCH v2 0/4] mtd: spi-nor: OTP support Michael Walle
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=6d52e1bdbbefc9383904e28bcc1c78a7@walle.cc \
--to=michael@walle.cc \
--cc=js07.lee@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=me@yadavpratyush.com \
--cc=miquel.raynal@bootlin.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
all inboxes | Powered by JetHome®