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: Sat, 19 Apr 2025 21:25:09 +0530 [thread overview]
Message-ID: <a6a154cd-ea98-4d27-a9a1-e8b39a5c77cc@gmail.com> (raw)
In-Reply-To: <aAMwri9RK2oNuC_p@antec>
Hi,
On 4/19/25 10:42 AM, Stafford Horne wrote:
> On Fri, Apr 18, 2025 at 06:04:29PM +0530, Sahil Siddiq wrote:
>> On 4/18/25 3:30 PM, Stafford Horne wrote:
>>> On Fri, Apr 18, 2025 at 02:42:20PM +0530, Sahil Siddiq wrote:
>>> [...]
>>> 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.
>
> Yes, please do this.
I have sent a new patch series. The email ids should match now. I have also
addressed the build warning that had appeared earlier so those changes won't
have to be made manually using "git fixup".
Thanks,
Sahil
prev parent reply other threads:[~2025-04-19 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 20:01 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
2025-04-19 5:12 ` Stafford Horne
2025-04-19 15:55 ` Sahil Siddiq [this message]
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=a6a154cd-ea98-4d27-a9a1-e8b39a5c77cc@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
all inboxes | Powered by JetHome®