Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: alsa-devel@alsa-project.org, stable@vger.kernel.org,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] sound: USB: line6: use dynamic buffers
Date: Sun, 28 Apr 2019 20:39:17 +0000	[thread overview]
Message-ID: <20190428203918.2B415206C1@mail.kernel.org> (raw)
In-Reply-To: <20190428160411.GA12815@kroah.com>

Hi,

[This is an automated email]

This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all

The bot has tested the following trees: v5.0.10, v4.19.37, v4.14.114, v4.9.171, v4.4.179, v3.18.139.

v5.0.10: Build OK!
v4.19.37: Build OK!
v4.14.114: Failed to apply! Possible dependencies:
    a8eaad7b04ea ("ALSA: line6: stop using get_seconds()")

v4.9.171: Failed to apply! Possible dependencies:
    a8eaad7b04ea ("ALSA: line6: stop using get_seconds()")

v4.4.179: Failed to apply! Possible dependencies:
    790869dacc3d ("ALSA: line6: Add support for POD X3")
    97d78acfb870 ("ALSA: line6: Allow different channel numbers for in/out")
    a8eaad7b04ea ("ALSA: line6: stop using get_seconds()")

v3.18.139: Failed to apply! Possible dependencies:
    16d603d32d34 ("staging: line6: Move audio endpoints to properties")
    25a0707cf6bc ("ALSA: line6: Improve line6_read/write_data() interfaces")
    410dca8d99ae ("staging: line6: Define a device type enum")
    4cb1a4ae4afb ("staging: line6: Rename capability macros")
    4d947546c3fb ("staging: line6: Use explicit indexes when defining properties")
    5c3396f909aa ("staging: line6: Remove `device_bit' from properties")
    61864d844c29 ("ALSA: move line6 usb driver into sound/usb")
    790869dacc3d ("ALSA: line6: Add support for POD X3")
    7b3e4d47ca37 ("staging: line6: List out capabilities individually")
    7b9584fa1c0b ("staging: line6: Move altsetting to properties")
    951dd316119c ("staging: line6: Split out POD HD500 interfaces")
    9e165be72f49 ("staging: line6: Move control endpoints to properties")
    ccddbe4a9953 ("ALSA: line6: Split to each driver")
    daf54a59f37c ("staging: line6: Cleanup device table")
    e474e7fd404b ("ALSA: line6: Return EIO if read/write not successful")
    e64e94df9916 ("ALSA: line6: Add delay before reading status")
    f3dfd1be08cc ("ALSA: line6: Return error if device not responding")
    f45be7dcc9e5 ("staging: line6: Remove idVendor and idProduct macros")


How should we proceed with this patch?

--
Thanks,
Sasha

      parent reply	other threads:[~2019-04-28 20:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-28 16:04 [PATCH] sound: USB: line6: use dynamic buffers Greg Kroah-Hartman
2019-04-28 16:42 ` Takashi Iwai
2019-04-28 17:07   ` Greg Kroah-Hartman
2019-04-28 20:39 ` Sasha Levin [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=20190428203918.2B415206C1@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=perex@perex.cz \
    --cc=stable@vger.kernel.org \
    --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