From: "Bean Huo (beanhuo)" <beanhuo@micron.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: "Tudor.Ambarus@microchip.com" <Tudor.Ambarus@microchip.com>,
"richard@nod.at" <richard@nod.at>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
Boris Brezillon <bbrezillon@kernel.org>
Subject: RE: [EXT] Re: [PATCH v2] mtd: spi-nor: Fix wrong abbreviation HWCPAS
Date: Fri, 8 Feb 2019 18:57:18 +0000 [thread overview]
Message-ID: <BYAPR08MB453343DF172ED508C736C94CDB690@BYAPR08MB4533.namprd08.prod.outlook.com> (raw)
In-Reply-To: <7278fa87-bfe4-3d95-9a9a-5ef4c0277d78@gmail.com>
>> git send-email 0001-mtd-spi-nor-Fix-wrong-abbreviation-HWCPAS.patch
>> 0001-mtd-spi-nor-Fix-wrong-abbreviation-HWCPAS.patch
>
>git send-email --annotate --to=... --cc=... --cc=... 000*patch
>
>This will likely make your life easier, rather than having to paste various email
>addresses to git send-email queries.
>
Yes, thanks.
>[...]
>
>--
>Best regards,
>Marek Vasut
>
>______________________________________________________
>Linux MTD discussion mailing list
>http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-02-08 18:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 14:23 [PATCH v2] mtd: spi-nor: Fix wrong abbreviation HWCPAS Bean Huo (beanhuo)
2019-02-08 14:43 ` Tudor.Ambarus
2019-02-08 15:07 ` [EXT] " Bean Huo (beanhuo)
2019-02-08 15:27 ` Bean Huo (beanhuo)
2019-02-08 15:51 ` Tudor.Ambarus
2019-02-08 17:13 ` Bean Huo (beanhuo)
2019-02-08 17:47 ` Boris Brezillon
2019-02-08 18:43 ` Bean Huo (beanhuo)
2019-02-08 18:46 ` Marek Vasut
2019-02-08 18:57 ` Bean Huo (beanhuo) [this message]
2019-02-08 18:50 ` Boris Brezillon
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=BYAPR08MB453343DF172ED508C736C94CDB690@BYAPR08MB4533.namprd08.prod.outlook.com \
--to=beanhuo@micron.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
/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).