From: Michael Walle <michael@walle.cc>
To: Vlim <vlim@gigadevice.com>
Cc: Victor Lim <victorswlim@gmail.com>,
tudor.ambarus@microchip.com, p.yadav@ti.com,
miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
vikhyat.goyal@amd.com, amit.kumar-mahapatra@amd.com,
alejandro.carmona@amd.com
Subject: Re: [PATCH] Linux: SPI: add Gigadevice part #
Date: Tue, 06 Dec 2022 09:17:43 +0100 [thread overview]
Message-ID: <d147146428a078bd01ddbb5c1a9a65ce@walle.cc> (raw)
In-Reply-To: <TY0PR06MB5658B73E2F22472D0AF48BDBBB1B9@TY0PR06MB5658.apcprd06.prod.outlook.com>
Hi,
Am 2022-12-06 02:27, schrieb Vlim:
> I will redo the patch following this doc.
> At the meantime, can you point out a few mistakes that I am making so
> that I can correct it in the next submit.
I really don't know what you want to achieve with this patch. It
has a bunch of renames. So what is the intention of the renames?
-michael
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-12-06 8:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 8:00 [PATCH] Linux: SPI: add Gigadevice part # Victor Lim
2022-12-05 8:22 ` Michael Walle
[not found] ` <TY0PR06MB5658B73E2F22472D0AF48BDBBB1B9@TY0PR06MB5658.apcprd06.prod.outlook.com>
2022-12-06 8:17 ` Michael Walle [this message]
2022-12-06 8:18 ` Miquel Raynal
[not found] ` <TY0PR06MB5658CAF1B83FF3CF92846AA0BB1B9@TY0PR06MB5658.apcprd06.prod.outlook.com>
2022-12-06 8:44 ` Miquel Raynal
2022-12-06 11:37 ` Frieder Schrempf
2022-12-06 11:44 ` Frieder Schrempf
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=d147146428a078bd01ddbb5c1a9a65ce@walle.cc \
--to=michael@walle.cc \
--cc=alejandro.carmona@amd.com \
--cc=amit.kumar-mahapatra@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
--cc=victorswlim@gmail.com \
--cc=vigneshr@ti.com \
--cc=vikhyat.goyal@amd.com \
--cc=vlim@gigadevice.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