From: Markus Elfring <Markus.Elfring@web.de>
To: Jeff Hugo <jeff.hugo@oss.qualcomm.com>,
dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Miaoqian Lin <linmq006@gmail.com>,
Carl Vanderlip <carl.vanderlip@oss.qualcomm.com>,
Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
Oded Gabbay <ogabbay@kernel.org>
Subject: Re: [PATCH] accel/qaic: Use pointer from memcpy() call for assignment in copy_partial_exec_reqs()
Date: Fri, 31 Oct 2025 17:35:37 +0100 [thread overview]
Message-ID: <31f4b885-7576-4422-b110-0ae5ceb34ff6@web.de> (raw)
In-Reply-To: <04645402-1e62-42cb-a8ff-3e5f8d852ea5@oss.qualcomm.com>
>>>> From: Markus Elfring <elfring@users.sourceforge.net>
>>>> Date: Fri, 31 Oct 2025 11:26:33 +0100
>>>> …
>>>> Signed-off-by: Markus Elfring <elfring@users.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@web.de>".
This can be fine.
> There is no SOB from "Markus Elfring <Markus.Elfring@web.de>" therefore "Markus Elfring <Markus.Elfring@web.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@web.de>" or "Markus Elfring <Markus.Elfring@web.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
prev parent reply other threads:[~2025-10-31 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 10:34 Markus Elfring
2025-10-31 15:30 ` Jeff Hugo
2025-10-31 15:34 ` Markus Elfring
2025-10-31 16:10 ` Jeff Hugo
2025-10-31 16:35 ` Markus Elfring [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=31f4b885-7576-4422-b110-0ae5ceb34ff6@web.de \
--to=markus.elfring@web.de \
--cc=carl.vanderlip@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linmq006@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ogabbay@kernel.org \
/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®