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: <31f4b885-7576-4422-b110-0ae5ceb34ff6@web.de>
Date: Fri, 31 Oct 2025 17:35:37 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Jeff Hugo <jeff.hugo@....qualcomm.com>, dri-devel@...ts.freedesktop.org,
 linux-arm-msm@...r.kernel.org
Cc: LKML <linux-kernel@...r.kernel.org>, kernel-janitors@...r.kernel.org,
 Miaoqian Lin <linmq006@...il.com>,
 Carl Vanderlip <carl.vanderlip@....qualcomm.com>,
 Jacek Lawrynowicz <jacek.lawrynowicz@...ux.intel.com>,
 Oded Gabbay <ogabbay@...nel.org>
Subject: Re: [PATCH] accel/qaic: Use pointer from memcpy() call for assignment
 in copy_partial_exec_reqs()

>>>> From: Markus Elfring <elfring@...rs.sourceforge.net>
>>>> Date: Fri, 31 Oct 2025 11:26:33 +0100
>>>> …
>>>> Signed-off-by: Markus Elfring <elfring@...rs.sourceforge.net>
>>>
>>> This does not match the address this patch was received from, therefore DCO does not appear to be satisfied.  I cannot accept this.
>>
>> I find such a change rejection questionable.
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.18-rc3#n409
> 
> I received this patch from "Markus Elfring <Markus.Elfring@....de>".

This can be fine.


> There is no SOB from "Markus Elfring <Markus.Elfring@....de>" therefore "Markus Elfring <Markus.Elfring@....de>" has not followed the DCO.

Are you aware how author information can be better preserved for patches?


> The resolution to this is either the author and the SOB change to "Markus Elfring <Markus.Elfring@....de>" or "Markus Elfring <Markus.Elfring@....de>" adds a SOB at the end to show the path the patch took (reference the paragraph in the documentation you linked to, starting at line 449).

There are obviously two email addresses which refer to me.

Would you be willing to clarify the proposed change possibility another bit?
(Would another patch variant become relevant for the affected software component at all?)

Regards,
Markus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ