linux-openrisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sahil Siddiq <icegambit91@gmail.com>
To: Stafford Horne <shorne@gmail.com>
Cc: jonas@southpole.se, stefan.kristiansson@saunalahti.fi,
	sahilcdq@proton.me, linux-openrisc@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] openrisc: Fix build warning in cache.c
Date: Fri, 18 Apr 2025 18:04:29 +0530	[thread overview]
Message-ID: <64beb3b4-a8fa-4acd-a139-6c19de0e37f4@gmail.com> (raw)
In-Reply-To: <aAIivK7NDG-6_aIU@antec>

Hi,

On 4/18/25 3:30 PM, Stafford Horne wrote:
> On Fri, Apr 18, 2025 at 02:42:20PM +0530, Sahil Siddiq wrote:
>> On 4/18/25 1:17 PM, Stafford Horne wrote:
>>> On Fri, Apr 04, 2025 at 10:39:22AM +0530, Sahil Siddiq wrote:
>>> [...]
>>> I was working on getting this patches ready for upstreaming and noticed one
>>> thing:
>>>
>>>       ---------------------------------------------------------------------------------------
>>>       ./patches/or1k-20250418/0001-openrisc-Refactor-struct-cpuinfo_or1k-to-reduce-dupl.patch
>>>       ---------------------------------------------------------------------------------------
>>>       WARNING: From:/Signed-off-by: email address mismatch: 'From: Sahil Siddiq <icegambit91@gmail.com>' != 'Signed-off-by: Sahil Siddiq <sahilcdq@proton.me>'
>>>
>>>       total: 0 errors, 1 warnings, 102 lines checked
>>>
>>> As you can see above the scripts/checkpatch.pl is failing with the warning
>>> about your email and signed-off-by not matching.  You can see more about it
>>> in the FROM_SIGN_OFF_MISMATCH section of the checkpatch[0] docs.
>>
>> Ok, this makes sense. I configured git-send-email to use gmail because
>> protonmail does not work with git-send-email without a paid account.
>>
>>> How would you like to resolve this?
>>
>> Is this a warning that cannot be ignored? I can:
>>
>> 1. submit the patch series with another email address that won't have issues
>>     with git-send-email, or
>> 2. submit the patch series using protonmail's web client (which might not be
>>     the best option).
>>
>> I would prefer not to use "icegambit91" in the signed-off-by tag.
>>
>> What are your thoughts on this?
> 
> I could rewrite the from header to match sahilcdq@proton.me.
> 
> But if I do that you should find a way to get proton.me to work with
> gi-send-email [0] for future commits.  It seems this can work using the
> Protonmail Bridge[1], though this site also says proton.me is not so good for
> using with git send email.

Right. Also, protonmail bridge requires a paid proton account.

> Maybe using another email in signed-off-by would be better.  The current
> patches are on linux-next[2] where we can see the From/Signed-off-by mismatch.
> For example:
> 
>      author	Sahil Siddiq <icegambit91@gmail.com>	2025-03-29 15:16:22 +0530
>      committer	Stafford Horne <shorne@gmail.com>	2025-03-29 10:22:21 +0000
>      commit	af83ece87a1ef5097434b7c3c1fc0e9e7b83b192 (patch)
> 
>      ...
> 
>      Signed-off-by: Sahil Siddiq <sahilcdq@proton.me>
>      Signed-off-by: Stafford Horne <shorne@gmail.com>
> 

I agree. I have another email id (sahilcdq0@gmail.com). I can configure git
to use this and this can also be used in the signed-off-by tag. So, this id
shouldn't cause an issue.

Let me know if I should send the series using this email id.

Thanks,
Sahil


  reply	other threads:[~2025-04-18 12:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01 20:01 [PATCH] openrisc: Fix build warning in cache.c Sahil Siddiq
2025-04-03 14:06 ` Stafford Horne
2025-04-04  5:09   ` Sahil Siddiq
2025-04-18  7:47     ` Stafford Horne
2025-04-18  9:12       ` Sahil Siddiq
2025-04-18 10:00         ` Stafford Horne
2025-04-18 12:34           ` Sahil Siddiq [this message]
2025-04-19  5:12             ` Stafford Horne
2025-04-19 15:55               ` Sahil Siddiq

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=64beb3b4-a8fa-4acd-a139-6c19de0e37f4@gmail.com \
    --to=icegambit91@gmail.com \
    --cc=jonas@southpole.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-openrisc@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=sahilcdq@proton.me \
    --cc=shorne@gmail.com \
    --cc=stefan.kristiansson@saunalahti.fi \
    /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).