From: Takashi Iwai <tiwai@suse.de>
To: Angel J <iamanaws@httpd.dev>
Cc: Takashi Iwai <tiwai@suse.de>,
linux-sound@vger.kernel.org, tiwai@suse.com, perex@perex.cz,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Fix the Dell XPS 8940 headset microphone
Date: Tue, 10 Nov 2026 15:12:42 +0100 [thread overview]
Message-ID: <87bj7wvkpx.wl-tiwai@suse.de> (raw)
In-Reply-To: <57Kgu-Pdq28OE2JHZjO7YEuS6RCOZLFiDoZO8uqMUieYwA58mHOkRbbZADWKNQsocsNCzH1GkU4pSEhpi-l3mZenIkWdjdNsOHVlbAxGsXQ=@httpd.dev>
On Tue, 10 Nov 2026 14:36:18 +0100,
Angel J wrote:
>
> On Monday, November 9th, 2026 at 22:02, Takashi Iwai <tiwai@suse.de> wrote:
> > On Mon, 09 Nov 2026 18:58:47 +0100,
> > Angel J wrote:
> > > Thanks for reviewing. My understanding is that the guidelines require
> > > a known identity, without necessarily requiring disclosure of a full
> > > name. I consistently use “Angel J” and this email address for kernel
> > > contributions. My PCI fix, commit 8805840aad73, was merged with the same
> > > author identity and Signed-off-by.
> >
> > Is your identity really already widely known in the kernel community?
> > I see only one recent commit in the past, and I can't see it's really
> > "known".
>
> Hi Takashi,
>
> No, I'm a new contributor and not widely known, and a full name would
> not change that.
As Signed-off-by tag is a legal requirement, giving a full name makes
the identity obviously clearer.
> I don't read "known identity" as requiring it, though.
> Documentation/process/submitting-patches.rst asks for "a known identity
> (sorry, no anonymous contributions.)", which I understand as excluding
> anonymous contributions rather than requiring a full name.
>
> "Angel J" is the name I use consistently for my public work, and I can
> be reached at this address.
>
> Let me know if you read the guideline differently.
>
> Thanks,
> Angel J
Honestly speaking, the problem is that I don't know you, so I can't
trust. If you have been involved with the kernel development long
enough, e.g. already appearing with "Angel J" in many threads or
commits, then it could be a good sign that it's a trustable known
identity. But it doesn't look like that for now...
thanks,
Takashi
next prev parent reply other threads:[~2026-11-10 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 15:03 Angel J
2026-11-04 7:15 ` Takashi Iwai
2026-11-09 17:58 ` Angel J
2026-11-10 6:02 ` Takashi Iwai
2026-11-10 13:36 ` Angel J
2026-11-10 14:12 ` Takashi Iwai [this message]
2026-11-10 16:24 ` Angel J
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=87bj7wvkpx.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=iamanaws@httpd.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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®