From: Takashi Iwai <tiwai@suse.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org,
Rolf Anderegg <rolf.anderegg@weiss.ch>,
Michele Perrone <michele.perrone@weiss.ch>
Subject: Re: [PATCH] ALSA: dice: add stream format parameters for Weiss devices
Date: Thu, 10 Aug 2023 08:36:20 +0200 [thread overview]
Message-ID: <87jzu3cskb.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230809225722.GA895382@workstation.local>
On Thu, 10 Aug 2023 00:57:22 +0200,
Takashi Sakamoto wrote:
>
> On Wed, Aug 09, 2023 at 04:39:55PM +0200, Takashi Iwai wrote:
> > On Wed, 09 Aug 2023 16:18:54 +0200,
> > Takashi Sakamoto wrote:
> > >
> > > Hi,
> > >
> > > On Wed, Aug 09, 2023 at 04:03:00PM +0200, Takashi Iwai wrote:
> > > > On Wed, 09 Aug 2023 02:26:31 +0200,
> > > > Takashi Sakamoto wrote:
> > > > >
> > > > > This patch is for kernel prepatch v6.5.
> > > >
> > > > Why it must be included in 6.5? This sounds more like a new
> > > > implementation, rather than an urgent but fix that is needed for rc.
> > >
> > > Thanks for your notice to the patch. Indeed, it is neither urgent nor
> > > bug fix. It is a kind of 'adding support for new device with slight
> > > change', like adding new entries in mod device table. The overall change
> > > and new lines are quite typical in ALSA dice driver, like TC Electronic
> > > devices in 'sound/firewire/dice/dice-tcelectronic.c'. Things are
> > > prepared and not brand-new.
> > >
> > > Precisely, current ALSA dice driver supports the Weiss models already,
> > > while the functionality is limited that the part of sampling transfer
> > > frequencies are available as the initial author said (e.g. when 44.1/48.0
> > > kHz are available, 88.2/96.0 kHz are not, vise versa). The patch extends
> > > the functionality by hard-coding stream formats following to the design
> > > of ALSA dice driver.
> > >
> > > Of cource, I don't mind postponing the patch to v6.6 kernel, but in my
> > > point of view, it is worth to v6.5 since users got benefits from the
> > > code which is not so novel.
> >
> > OK, then I'd rather put it to 6.6.
> > If it were for rc2, I could take it. But it's already in a second
> > half turn, and I'd rather like to limit the changes for later rcs.
>
> It sounds reasonable. So should I post the patch on your for-next branch?
No need for that, the patch itself is applicable cleanly.
I just need to drop the commit log line indicating 6.5-rc.
thanks,
Takashi
next prev parent reply other threads:[~2023-08-10 6:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 0:26 [PATCH] ALSA: dice: add stream format parameters for Weiss devices Takashi Sakamoto
2023-08-09 14:03 ` Takashi Iwai
2023-08-09 14:18 ` Takashi Sakamoto
2023-08-09 14:39 ` Takashi Iwai
2023-08-09 22:57 ` Takashi Sakamoto
2023-08-10 6:36 ` Takashi Iwai [this message]
2023-08-10 11:06 ` Takashi Sakamoto
-- strict thread matches above, loose matches on Subject: below --
2023-07-28 9:16 Michele Perrone
2023-07-28 13:13 ` Takashi Sakamoto
2023-07-31 8:09 ` Michele Perrone
2023-07-31 14:06 ` Takashi Sakamoto
2023-08-08 8:34 ` Michele Perrone
2023-08-08 15:25 ` Takashi Sakamoto
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=87jzu3cskb.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=michele.perrone@weiss.ch \
--cc=o-takashi@sakamocchi.jp \
--cc=rolf.anderegg@weiss.ch \
/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;
as well as URLs for NNTP newsgroup(s).