From: Marek Szyprowski <m.szyprowski@samsung.com>
To: yzddMr6 <yzddmr6@gmail.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dma: swiotlb: Allocate the restricted DMA pool slot array with kvzalloc()
Date: Fri, 20 Nov 2026 16:26:17 +0100 [thread overview]
Message-ID: <a58ae41b-4ee6-44d6-bd4c-56e51b19df60@samsung.com> (raw)
In-Reply-To: <CAB63uaFw9QjjN131UjiJvpp6qHM+xw+-9wEcujuNoYVzhmXtOQ@mail.gmail.com>
On 20.11.2026 16:22, yzddMr6 wrote:
> On 20.11.2026 15:18, Marek Szyprowski wrote:
>> The change looks fine, but according to kernel rules, the patch must be
>> signed with a real developer name. 'yzddMr6' doesn't look like a real name.
> Hi Marek,
>
> Thanks for looking at it.
>
> yzddMr6 is the name I use consistently for my kernel work, and mail to
> the address in the From: and Signed-off-by: lines reaches me. Since
> commit d4563201f33a ("Documentation: simplify and clarify DCO
> contribution example language"), submitting-patches.rst asks for a
> known identity rather than a legal name, and that commit notes that
> nicknames have always been accepted. Mark Brown applied a patch of mine
> under this name to the sound tree earlier this week (bd6e011c8121).
>
> If you still need a legal name in the sign-off, mine is Zhendong Liu;
> let me know and I will send a v2 signed off as
> "Zhendong Liu <yzddmr6@gmail.com>".
I would prefer that.
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
prev parent reply other threads:[~2026-11-20 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20261120131146eucas1p2d05549af0404d6af77ce3e9385e91fa7@eucas1p2.samsung.com>
2026-11-20 13:11 ` yzddMr6 via B4 Relay
2026-11-20 14:18 ` Marek Szyprowski
2026-11-20 15:22 ` yzddMr6
2026-11-20 15:26 ` Marek Szyprowski [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=a58ae41b-4ee6-44d6-bd4c-56e51b19df60@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=yzddmr6@gmail.com \
/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®