From: Boris Brezillon <bbrezillon@kernel.org>
To: "Bean Huo (beanhuo)" <beanhuo@micron.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>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>
Subject: Re: [EXT] Re: [PATCH v2] mtd: spi-nor: Fix wrong abbreviation HWCPAS
Date: Fri, 8 Feb 2019 18:47:18 +0100 [thread overview]
Message-ID: <20190208184718.3c488d0d@kernel.org> (raw)
In-Reply-To: <BYAPR08MB4533DB0A7F4E30543750C83FDB690@BYAPR08MB4533.namprd08.prod.outlook.com>
Hi Bean,
On Fri, 8 Feb 2019 17:13:52 +0000
"Bean Huo (beanhuo)" <beanhuo@micron.com> wrote:
> Hi, Tutor
> Thanks. unfortunately, it doesn't work on my side. Problem is on our email server side, not my local setting.
> I followed your configuration, then git-email failed.
Can you paste the output of git send-email and the [sendemail] section
of your .gitconfig so we can check.
It shouldn't fail, really, because the server shouldn't check the body
section of your email, and this is where the extra
From: First Last <foo@bar.com>
line is placed.
> Please just change my S-o-b to 'Bean Huo (beanhuo) <beanhuo@micron.com>' in my patch to please checkpacth.pl. It is not huge change.
It's not a problem when an drive-by contributor posts a patch, but if
you don't patch it that means we'll have to do it manually every time
we apply one of your patch, so please find a solution.
Thanks,
Boris
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-02-08 17:47 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 [this message]
2019-02-08 18:43 ` Bean Huo (beanhuo)
2019-02-08 18:46 ` Marek Vasut
2019-02-08 18:57 ` Bean Huo (beanhuo)
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=20190208184718.3c488d0d@kernel.org \
--to=bbrezillon@kernel.org \
--cc=Tudor.Ambarus@microchip.com \
--cc=beanhuo@micron.com \
--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).