All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Simon Horman <horms@verge.net.au>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Marek Vasut <marek.vasut+renesas@gmail.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [PATCH V6] ARM: shmobile: Rework the PMIC IRQ line quirk
Date: Wed, 19 Sep 2018 11:36:05 +0200	[thread overview]
Message-ID: <70fff432-001e-7161-ab47-b600161ec257@gmail.com> (raw)
In-Reply-To: <CAMuHMdVR-P-3s6Z0=GSa310ty+cqQk0WOO3w7+ZgiwkAt0Riiw@mail.gmail.com>

On 09/19/2018 11:30 AM, Geert Uytterhoeven wrote:
> Hi Marek,
> 
> On Wed, Sep 19, 2018 at 11:28 AM Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
>> On Wed, Sep 19, 2018 at 11:22 AM Marek Vasut <marek.vasut@gmail.com> wrote:
>>> On 09/19/2018 11:13 AM, Simon Horman wrote:
>>>> Marek, these days checkpatch complains if the author of the patch does not
>>>> have a signed offline, and the inconsistency between your
>>>> from and Sign-off the email address trips that check.
>>>>
>>>> Could you consider either a) enhancing checkpatch or b) using
>>
>> I'm the one who enhanced checkpatch with the new check ;-)
>>
>>>> the same address twice? No need to take any action for this patch.
>>>
>>> Sure, do you know if there's some tweak to git config , so git
>>> send-email uses the m.v+foo@ From address ?
>>
>> Git send-email uses the address from user.email in gitconfig, just
>> like git commit.
>>
>> However, I see you're using Gmail's SMTP server. That one replaces the
>> From-line in the header by your primary email address as configured in Gmail
>> (even if you have configured Gmail to know the other address is yours, too).
>>
>> I use my ISP's SMTP server to work around that.
> 
> Another trick that should work:
> 
> If you run git send-email in a repo with a different user.email
> config, it should
> add the original From to the email's body, as it will detect you're submitting
> patches on behalf of "someone else".

Or I can just patch in the From field myself before sending , just like
Cc: and SoB ?

-- 
Best regards,
Marek Vasut

WARNING: multiple messages have this Message-ID (diff)
From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V6] ARM: shmobile: Rework the PMIC IRQ line quirk
Date: Wed, 19 Sep 2018 11:36:05 +0200	[thread overview]
Message-ID: <70fff432-001e-7161-ab47-b600161ec257@gmail.com> (raw)
In-Reply-To: <CAMuHMdVR-P-3s6Z0=GSa310ty+cqQk0WOO3w7+ZgiwkAt0Riiw@mail.gmail.com>

On 09/19/2018 11:30 AM, Geert Uytterhoeven wrote:
> Hi Marek,
> 
> On Wed, Sep 19, 2018 at 11:28 AM Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
>> On Wed, Sep 19, 2018 at 11:22 AM Marek Vasut <marek.vasut@gmail.com> wrote:
>>> On 09/19/2018 11:13 AM, Simon Horman wrote:
>>>> Marek, these days checkpatch complains if the author of the patch does not
>>>> have a signed offline, and the inconsistency between your
>>>> from and Sign-off the email address trips that check.
>>>>
>>>> Could you consider either a) enhancing checkpatch or b) using
>>
>> I'm the one who enhanced checkpatch with the new check ;-)
>>
>>>> the same address twice? No need to take any action for this patch.
>>>
>>> Sure, do you know if there's some tweak to git config , so git
>>> send-email uses the m.v+foo@ From address ?
>>
>> Git send-email uses the address from user.email in gitconfig, just
>> like git commit.
>>
>> However, I see you're using Gmail's SMTP server. That one replaces the
>> From-line in the header by your primary email address as configured in Gmail
>> (even if you have configured Gmail to know the other address is yours, too).
>>
>> I use my ISP's SMTP server to work around that.
> 
> Another trick that should work:
> 
> If you run git send-email in a repo with a different user.email
> config, it should
> add the original From to the email's body, as it will detect you're submitting
> patches on behalf of "someone else".

Or I can just patch in the From field myself before sending , just like
Cc: and SoB ?

-- 
Best regards,
Marek Vasut

  reply	other threads:[~2018-09-19 15:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-18 12:23 [PATCH V6] ARM: shmobile: Rework the PMIC IRQ line quirk Marek Vasut
2018-09-18 12:23 ` Marek Vasut
2018-09-18 12:52 ` Geert Uytterhoeven
2018-09-18 12:52   ` Geert Uytterhoeven
2018-09-19  9:13   ` Simon Horman
2018-09-19  9:13     ` Simon Horman
2018-09-19  9:21     ` Marek Vasut
2018-09-19  9:21       ` Marek Vasut
2018-09-19  9:28       ` Geert Uytterhoeven
2018-09-19  9:28         ` Geert Uytterhoeven
2018-09-19  9:30         ` Geert Uytterhoeven
2018-09-19  9:30           ` Geert Uytterhoeven
2018-09-19  9:36           ` Marek Vasut [this message]
2018-09-19  9:36             ` Marek Vasut
2018-09-19  9:38             ` Geert Uytterhoeven
2018-09-19  9:38               ` Geert Uytterhoeven
2018-09-19  9:41       ` Simon Horman
2018-09-19  9:41         ` Simon Horman

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=70fff432-001e-7161-ab47-b600161ec257@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=marek.vasut+renesas@gmail.com \
    --cc=wsa+renesas@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.