lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a6a154cd-ea98-4d27-a9a1-e8b39a5c77cc@gmail.com>
Date: Sat, 19 Apr 2025 21:25:09 +0530
From: Sahil Siddiq <icegambit91@...il.com>
To: Stafford Horne <shorne@...il.com>
Cc: jonas@...thpole.se, stefan.kristiansson@...nalahti.fi,
 sahilcdq@...ton.me, linux-openrisc@...r.kernel.org,
 linux-kernel@...r.kernel.org, kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] openrisc: Fix build warning in cache.c

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@...il.com>	2025-03-29 15:16:22 +0530
>>>       committer	Stafford Horne <shorne@...il.com>	2025-03-29 10:22:21 +0000
>>>       commit	af83ece87a1ef5097434b7c3c1fc0e9e7b83b192 (patch)
>>>
>>>       ...
>>>
>>>       Signed-off-by: Sahil Siddiq <sahilcdq@...ton.me>
>>>       Signed-off-by: Stafford Horne <shorne@...il.com>
>>>
>>
>> I agree. I have another email id (sahilcdq0@...il.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ