All of lore.kernel.org
 help / color / mirror / Atom feed
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 07:02:29 +0100	[thread overview]
Message-ID: <877bilusui.wl-tiwai@suse.de> (raw)
In-Reply-To: <5ncUNWXphcObbYD04quaQMbD0tGoekaHB-QQrX5tgC7sSbzoT9jRVrbY9PyT6mRbww0G9-voA6Y98HjvPg7U25kmeybfQALp5NsNKym-3pc=@httpd.dev>

On Mon, 09 Nov 2026 18:58:47 +0100,
Angel J wrote:
> 
> On Tuesday, November 3rd, 2026 at 23:15, Takashi Iwai <tiwai@suse.de> wrote:
> > The code change looks OK, but could you resubmit with a proper
> > Signed-off-by tag with your full name (also From tag, too)?
> > Signed-off-by is a legal requirement.
> 
> Hi Takashi,
> 
> 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".


thanks,

Takashi

  reply	other threads:[~2026-11-10  6:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 15:03 [PATCH] ALSA: hda/realtek: Fix the Dell XPS 8940 headset microphone Angel J
2026-11-04  7:15 ` Takashi Iwai
2026-11-09 17:58   ` Angel J
2026-11-10  6:02     ` Takashi Iwai [this message]
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

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=877bilusui.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.