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: Wed, 11 Nov 2026 18:25:23 +0100 [thread overview]
Message-ID: <87y0azs2kc.wl-tiwai@suse.de> (raw)
In-Reply-To: <TDT6b_7cMUkRNo88Xj3i3Ji--f4WdAmawcBXuT3TmHzVrxy0Xhr6il-PPdh6dbodGGrapwWjGx1KWruC5fAjw0cV27lhGzJ0HRWJmLgfwrY=@httpd.dev>
On Tue, 10 Nov 2026 17:24:15 +0100,
Angel J wrote:
>
> On Tuesday, November 10th, 2026 at ..., Takashi Iwai <tiwai@suse.de> wrote:
> > 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...
>
> Hi Takashi,
>
> That is fair, I am new to kernel development. Outside the kernel I am
> an active open source contributor, mostly to NixOS, with over 100
> merged changes in nixpkgs and contributions to other projects from
> this account:
>
> https://github.com/iamanaws
>
> I am not comfortable publishing my full name in a public archive. If
> the above is not enough, is there another way I could establish the
> identity that would work for you?
Well, although I'm not comfortable with the situation, the code change
itself is so trivial and can't do anything seriously wrong -- so it's
not wise to delay it just because of that, and I took as is now.
thanks,
Takashi
prev parent reply other threads:[~2026-11-11 17:25 UTC|newest]
Thread overview: 8+ 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
2026-11-10 16:24 ` Angel J
2026-11-11 17:25 ` Takashi Iwai [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=87y0azs2kc.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®