From: Takashi Iwai <tiwai@suse.de>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Jaroslav Kysela <perex@perex.cz>,
ALSA development <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.com>, Mark Brown <broonie@kernel.org>,
Ivan Orlov <ivan.orlov0322@gmail.com>
Subject: Re: [PATCH] MAINTAINERS: ALSA: change mailing list to linux-sound on vger
Date: Wed, 25 Oct 2023 15:52:24 +0200 [thread overview]
Message-ID: <87o7gmx10n.wl-tiwai@suse.de> (raw)
In-Reply-To: <20231025-unique-dingo-of-proficiency-fa998c@meerkat>
On Wed, 25 Oct 2023 15:49:48 +0200,
Konstantin Ryabitsev wrote:
>
> On Wed, Oct 25, 2023 at 03:41:31PM +0200, Takashi Iwai wrote:
> > ... and I tested posting patches to linux-sound ML:
> > https://lore.kernel.org/linux-sound/20231025132314.5878-1-tiwai@suse.de
> >
> > I thought those are forwarded to alsa-devel, but apparently they
> > aren't.
>
> In case there was confusion, I meant that the patches sent to that list will
> be automatically fed to the alsa-devel patchwork, which they were:
>
> https://patchwork.kernel.org/project/alsa-devel/list/?series=796434
Ah I see.
> > So we all devs need to subscribe this ML now?
>
> Until we can do search-based pseudo-lists in the near future, that is indeed
> what I would recommend. There is almost no other traffic on that list, so this
> will not impact your inboxes in any meaningful way.
OK, thanks!
Takashi
prev parent reply other threads:[~2023-10-25 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 7:12 [PATCH] MAINTAINERS: ALSA: change mailing list to linux-sound on vger Jaroslav Kysela
2023-10-20 11:49 ` Mark Brown
2023-10-20 13:00 ` Konstantin Ryabitsev
2023-10-20 13:27 ` Ivan Orlov
2023-10-23 13:03 ` Takashi Iwai
2023-10-25 13:41 ` Takashi Iwai
2023-10-25 13:49 ` Konstantin Ryabitsev
2023-10-25 13:52 ` 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=87o7gmx10n.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ivan.orlov0322@gmail.com \
--cc=konstantin@linuxfoundation.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.