From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pavel Machek <pavel@denx.de>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Takashi Sakamoto <o-takashi@sakamocchi.jp>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH 4.19 1/8] ALSA; firewire-tascam: exclude Tascam FE-8 from detection
Date: Mon, 14 Sep 2020 09:58:58 +0200 [thread overview]
Message-ID: <20200914075858.GA1035258@kroah.com> (raw)
In-Reply-To: <20200914074731.GA11659@amd>
On Mon, Sep 14, 2020 at 09:47:31AM +0200, Pavel Machek wrote:
> Hi!
>
> > From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
> >
> > Tascam FE-8 is known to support communication by asynchronous transaction
> > only. The support can be implemented in userspace application and
> > snd-firewire-ctl-services project has the support. However, ALSA
> > firewire-tascam driver is bound to the model.
>
> This one is in upstream, but is not marked as such. AFAICT it is
> 0bd8bce897b6697bbc286b8ba473aa0705fe394b.
>
> Unfortunately it is too late to fix that now.
>
> This one was scheduled to be released at "Responses should be made by
> Sun, 13 Sep 2020 12:54:13 +0000.". But it was released day earlier:
> "Date: Sat, 12 Sep 2020 14:42:49 +0200".
>
> Could you actually follow published schedule?
If all of the reported testing systems come back successful, there is no
need to wait any longer.
> Could you cc me release announcements on pavel@denx.de email?
Will add you to the list, thanks.
greg k-h
next prev parent reply other threads:[~2020-09-14 7:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 12:54 [PATCH 4.19 0/8] 4.19.145-rc1 review Greg Kroah-Hartman
2020-09-11 12:54 ` [PATCH 4.19 1/8] ALSA; firewire-tascam: exclude Tascam FE-8 from detection Greg Kroah-Hartman
2020-09-14 7:47 ` Pavel Machek
2020-09-14 7:58 ` Greg Kroah-Hartman [this message]
2020-09-16 8:16 ` Pavel Machek
2020-09-11 12:54 ` [PATCH 4.19 2/8] block: ensure bdi->io_pages is always initialized Greg Kroah-Hartman
2020-09-11 12:54 ` [PATCH 4.19 3/8] netlabel: fix problems with mapping removal Greg Kroah-Hartman
2020-09-11 12:54 ` [PATCH 4.19 4/8] net: usb: dm9601: Add USB ID of Keenetic Plus DSL Greg Kroah-Hartman
2020-09-11 12:54 ` [PATCH 4.19 5/8] sctp: not disable bh in the whole sctp_get_port_local() Greg Kroah-Hartman
2020-09-11 12:54 ` [PATCH 4.19 6/8] tipc: fix shutdown() of connectionless socket Greg Kroah-Hartman
2020-09-11 12:54 ` [PATCH 4.19 7/8] net: disable netpoll on fresh napis Greg Kroah-Hartman
2020-09-11 12:54 ` [PATCH 4.19 8/8] net/mlx5e: Dont support phys switch id if not in switchdev mode Greg Kroah-Hartman
2020-09-11 22:23 ` [PATCH 4.19 0/8] 4.19.145-rc1 review Shuah Khan
2020-09-12 7:50 ` Naresh Kamboju
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=20200914075858.GA1035258@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o-takashi@sakamocchi.jp \
--cc=pavel@denx.de \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.de \
/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).