From: <Tudor.Ambarus@microchip.com>
To: <beanhuo@micron.com>, <linux-mtd@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: marek.vasut@gmail.com, computersforpeace@gmail.com,
dwmw2@infradead.org, bbrezillon@kernel.org, richard@nod.at
Subject: Re: [EXT] Re: [PATCH v2] mtd: spi-nor: Fix wrong abbreviation HWCPAS
Date: Fri, 8 Feb 2019 15:51:16 +0000 [thread overview]
Message-ID: <a83a9655-0ce7-da15-ec17-80ef88764e21@microchip.com> (raw)
In-Reply-To: <BYAPR08MB45335415CC3690816C1FD603DB690@BYAPR08MB4533.namprd08.prod.outlook.com>
Hi, Bean,
On 02/08/2019 05:27 PM, Bean Huo (beanhuo) wrote:
> Hi, Tutor
>
>> $ ./scripts/checkpatch.pl --strict
>> v2-mtd-spi-nor-Fix-wrong-abbreviation-HWCPAS.patch
>> WARNING: Missing Signed-off-by: line by nominal patch author 'Bean Huo
>> (beanhuo) <beanhuo@micron.com>'
>>
> I think, this is because of our email system, it always adds '(xxx)' between user name
> and email address.
> If you are convenient, please help fix since it is not such hug change.
I'm on a funny email server too, it keeps overwriting my email header "from
field". I have a workaround that might work for you too. Here's part of my
.gitconfig:
[user]
name = Tudor Ambarus
email = tudor.ambarus@microchip.com
[sendemail]
from = Tudor X Ambarus <tudor.ambarus@microchip.com>
Because my [sendemail] from field is different than my [user] name and email,
git send-email will add in the body of the patch the [user] name and email:
From: Tudor Ambarus <tudor.ambarus@microchip.com>
When the patch is applied, it takes the author name from the patch body. Even if
the server overwrites the from field from the header, it will be ignored.
Let me know if this works for you.
ta
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-02-08 15:51 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 [this message]
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)
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=a83a9655-0ce7-da15-ec17-80ef88764e21@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=bbrezillon@kernel.org \
--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).