From: Takashi Iwai <tiwai@suse.de>
To: Kailang <kailang@realtek.com>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: move alc892 to patch_alc882
Date: Mon, 07 Apr 2014 10:37:55 +0200 [thread overview]
Message-ID: <s5hmwfxmt5o.wl%tiwai@suse.de> (raw)
In-Reply-To: <5C8998C298284925B0366DDAC8B6717F@realtek.com.tw>
At Mon, 7 Apr 2014 14:04:34 +0800,
Kailang wrote:
>
>
> > At Sat, 5 Apr 2014 14:52:24 +0800,
> > Raymond Yau wrote:
> >>
> >> Hi Takashi,
> >>
> >> >
> >> > The original was patch to patch_alc662.
> >> > Move it into patch_alc882.
> >> >
> >> >
> >> is there any reason not including those PCI QUIRK for alc892 ?
> >
> > Because it's not clarified why this must be applied.
> > I'm waiting for the updated patch from Kailang.
> >
>
> Sorry!
> I just aligned the channel count.
> So, move the alc892 to patch_alc882.
As I already asked, could you resubmit the patch with the proper
changelog? You have to clarify why the patch is needed and how it's
solved in the patch changelog.
Takashi
>
> >
> > Takashi
> >
> > ------Please consider the environment before printing this e-mail.
>
next prev parent reply other threads:[~2014-04-07 8:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 9:47 move alc892 to patch_alc882 Kailang
2014-03-27 10:06 ` Takashi Iwai
2014-04-05 6:52 ` Raymond Yau
2014-04-06 7:58 ` Takashi Iwai
2014-04-07 6:04 ` Kailang
2014-04-07 8:37 ` Takashi Iwai [this message]
2014-04-07 8:59 ` Improve hp pop noise Kailang
2014-04-07 10:33 ` Takashi Iwai
2014-04-08 7:34 ` Change module name for Chrome Kailang
2014-04-08 7:58 ` Takashi Iwai
2014-04-08 8:06 ` Kailang
2014-04-08 8:39 ` Takashi Iwai
2014-04-08 8:56 ` Kailang
2014-04-08 9:22 ` Add eapd shutup to alc283 Kailang
2014-04-07 9:19 ` move alc892 to patch_alc882 Kailang
2014-04-07 11:11 ` Raymond Yau
2014-04-08 9:08 ` Kailang
2014-04-09 4:53 ` Raymond Yau
2014-04-09 6:30 ` Kailang
2014-04-09 7:24 ` Raymond Yau
2014-04-10 1:30 ` Raymond Yau
2014-04-10 1:44 ` Raymond Yau
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=s5hmwfxmt5o.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=kailang@realtek.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