From: Mario Limonciello <mario_limonciello@dell.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "(alsa-devel@alsa-project.org)" <alsa-devel@alsa-project.org>,
Kailang <kailang@realtek.com>
Subject: Re: Support Dell headset mode for ALC288
Date: Mon, 20 Apr 2015 15:12:59 -0500 [thread overview]
Message-ID: <55355DCB.8010300@dell.com> (raw)
In-Reply-To: <s5hmw2jnejt.wl-tiwai@suse.de>
On 04/08/2015 04:40 AM, Takashi Iwai wrote:
> At Wed, 8 Apr 2015 08:08:47 +0000,
> Kailang wrote:
> OK, I applied this with rephrasing the changelog mentioning ALC286,
> too.
>
> Since this one and Dell patch are relative large changes, I queued
> them to for-next branch instead of for-linus, i.e. the merge to Linus
> tree will be postponed to 4.1-rc1.
>
>
> thanks,
>
> Takashi
>
>
Takashi,
It's a bit unfortunate that these are landing in 4.1 rather than 4.0. 4.1 they actually won't be very useful in the default kernel due to this patch landing:
https://github.com/torvalds/linux/commit/b1ef2972586577e0ca9675254ee141f65a8824e5
With 4.1 the XPS 13 will run in I2S audio mode.
Is there any chance at backporting these to @stable? Some of the distros (Ubuntu and Fedora) are already backporting this into some of their kernel versions, but I think this should benefit the community at large if the other distributions that tracked @stable could pick this up too.
Thanks,
next prev parent reply other threads:[~2015-04-20 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6FAB7C47BCF00940BB0999A99BE3547A17A0C909@RTITMBSV09.realtek.com.tw>
2015-04-04 12:42 ` Support Dell headset mode for ALC288 Takashi Iwai
2015-04-07 7:08 ` Kailang
[not found] ` <6FAB7C47BCF00940BB0999A99BE3547A17A0D1AB@RTITMBSV09.realtek.com.tw>
2015-04-08 7:40 ` Takashi Iwai
2015-04-08 8:08 ` Kailang
2015-04-08 9:40 ` Takashi Iwai
2015-04-20 20:12 ` Mario Limonciello [this message]
2015-04-21 5:53 ` Takashi Iwai
[not found] ` <6FAB7C47BCF00940BB0999A99BE3547A17A0D1E8@RTITMBSV09.realtek.com.tw>
2015-04-08 9:41 ` 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=55355DCB.8010300@dell.com \
--to=mario_limonciello@dell.com \
--cc=alsa-devel@alsa-project.org \
--cc=kailang@realtek.com \
--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 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.