Linux Sound subsystem development
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Takashi Iwai <tiwai@suse.com>
Cc: Jaroslav Kysela <perex@perex.cz>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-sound@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Clemens Ladisch <clemens@ladisch.de>
Subject: [PATCH v2 0/9] ALSA: seq: Use bus specific probe and remove
Date: Tue,  9 Dec 2025 13:38:42 +0100	[thread overview]
Message-ID: <cover.1765283601.git.u.kleine-koenig@baylibre.com> (raw)

Hello,

here comes a v2 for my series previously posted at
https://lore.kernel.org/all/cover.1764677854.git.u.kleine-koenig@baylibre.com
.

The only change is fixing a build problem I introduced in the opl4
driver (and that I didn't notice because I usually compile test for
ARCH=arm64 where this driver isn't built).

Best regards
Uwe

Uwe Kleine-König (9):
  ALSA: seq: Use bus specific probe and remove
  ALSA: seq: midi: Convert to snd_seq bus probe mechanism
  ALSA: seq: ump: Convert to snd_seq bus probe mechanism
  ALSA: opl3: Convert to snd_seq bus probe mechanism
  ALSA: opl4: Convert to snd_seq bus probe mechanism
  ALSA: sb: Convert to snd_seq bus probe mechanism
  ALSA: emu10k1: Convert to snd_seq bus probe mechanism
  ALSA: seq: oss: Convert to snd_seq bus probe mechanism
  ALSA: seq: Refuse to probe seq drivers with non-bus probe or remove

 include/sound/seq_device.h         |  2 ++
 sound/core/seq/oss/seq_oss.c       |  4 ++--
 sound/core/seq/oss/seq_oss_synth.c | 12 ++++--------
 sound/core/seq/oss/seq_oss_synth.h |  4 ++--
 sound/core/seq/seq_midi.c          | 15 ++++++---------
 sound/core/seq/seq_ump_client.c    | 11 ++++-------
 sound/core/seq_device.c            | 26 +++++++++++++++++++++++++-
 sound/drivers/opl3/opl3_seq.c      | 13 +++++--------
 sound/drivers/opl4/opl4_seq.c      | 13 +++++--------
 sound/isa/sb/emu8000_synth.c       | 13 +++++--------
 sound/pci/emu10k1/emu10k1_synth.c  | 13 +++++--------
 11 files changed, 65 insertions(+), 61 deletions(-)


base-commit: 7d0a66e4bb9081d75c82ec4957c50034cb0ea449
-- 
2.47.3


             reply	other threads:[~2025-12-09 12:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-09 12:38 Uwe Kleine-König [this message]
2025-12-09 12:38 ` [PATCH v2 1/9] ALSA: seq: Use bus specific probe and remove Uwe Kleine-König
2025-12-09 12:38 ` [PATCH v2 2/9] ALSA: seq: midi: Convert to snd_seq bus probe mechanism Uwe Kleine-König
2025-12-09 12:38 ` [PATCH v2 3/9] ALSA: seq: ump: " Uwe Kleine-König
2025-12-09 12:38 ` [PATCH v2 4/9] ALSA: opl3: " Uwe Kleine-König
2025-12-09 12:38 ` [PATCH v2 5/9] ALSA: opl4: " Uwe Kleine-König
2025-12-09 12:38 ` [PATCH v2 6/9] ALSA: sb: " Uwe Kleine-König
2025-12-09 12:38 ` [PATCH v2 7/9] ALSA: emu10k1: " Uwe Kleine-König
2025-12-09 12:38 ` [PATCH v2 8/9] ALSA: seq: oss: " Uwe Kleine-König
2025-12-09 12:38 ` [PATCH v2 9/9] ALSA: seq: Refuse to probe seq drivers with non-bus probe or remove Uwe Kleine-König
2025-12-14 10:11 ` [PATCH v2 0/9] ALSA: seq: Use bus specific probe and remove 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=cover.1765283601.git.u.kleine-koenig@baylibre.com \
    --to=u.kleine-koenig@baylibre.com \
    --cc=clemens@ladisch.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=perex@perex.cz \
    --cc=tglx@linutronix.de \
    --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