From: Takashi Iwai <tiwai@suse.de>
To: x8svc <enscrpt@pm.me>
Cc: Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
Clemens Ladisch <clemens@ladisch.de>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] ALSA: usb-audio, ua101: oversized packet copies overrun PCM ring buffers
Date: Mon, 26 Oct 2026 14:38:31 +0100 [thread overview]
Message-ID: <875wyo60q0.wl-tiwai@suse.de> (raw)
In-Reply-To: <20261026122855.283-1-enscrpt@pm.me>
On Mon, 26 Oct 2026 13:30:07 +0100,
x8svc wrote:
>
> Takashi,
>
> Thanks for the review.
>
> x8svc is my standing identity, not a name picked for this one patch. The same
> name signs every commit I push and is the account behind my public GitHub
> work; I expect to keep using it for any future kernel submissions too.
Honestly speaking, I don't care about github activity at all. The
only question is the activity in the kernel community, and I don't see
any of such until now?
> Both patches already carry matching From and Signed-off-by lines
> (x8svc <enscrpt@pm.me>), so unless there's something more specific you need
> to treat it as a known identity, I'd rather not resubmit for no reason. Let
> me know if that's enough, or what else you need.
The Signed-off-by is the only concern.
thanks,
Takashi
next prev parent reply other threads:[~2026-10-26 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 0:10 x8svc
2026-10-26 0:10 ` [PATCH 1/2] ALSA: usb-audio: Bound packet copies by the PCM buffer size x8svc
2026-10-26 0:10 ` [PATCH 2/2] ALSA: ua101: " x8svc
2026-10-26 8:08 ` [PATCH 0/2] ALSA: usb-audio, ua101: oversized packet copies overrun PCM ring buffers Takashi Iwai
2026-10-26 12:30 ` x8svc
2026-10-26 13:38 ` Takashi Iwai [this message]
2026-10-26 22:40 ` Sinan Turunc
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=875wyo60q0.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=clemens@ladisch.de \
--cc=enscrpt@pm.me \
--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®