From: Kailang <kailang@realtek.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: " \(alsa-devel@alsa-project.org\)" <alsa-devel@alsa-project.org>
Subject: RE: ALC236 recording issue
Date: Thu, 7 Oct 2021 06:15:47 +0000 [thread overview]
Message-ID: <294ba24e55ba40bc83a00a4f24e8c779@realtek.com> (raw)
In-Reply-To: <s5h8rz6cu0l.wl-tiwai@suse.de>
Many Thanks. ^^
> -----Original Message-----
> From: Takashi Iwai <tiwai@suse.de>
> Sent: Wednesday, October 6, 2021 6:44 PM
> To: Kailang <kailang@realtek.com>
> Cc: (alsa-devel@alsa-project.org) <alsa-devel@alsa-project.org>
> Subject: Re: ALC236 recording issue
>
> On Wed, 06 Oct 2021 11:14:40 +0200,
> Kailang wrote:
> >
> > Hi Takashi,
> >
> > I couldn't find this apply record on git.kernel.org.
> > HP guy want me to provide the patch URL.
>
> It wasn't pushed out properly, sorry. Now it's public, found in the commit
> 5aec98913095ed3b4424ed6c5fdeb6964e9734da.
>
>
> Takashi
>
> >
> > BR,
> > Kailang
> >
> > > -----Original Message-----
> > > From: Takashi Iwai <tiwai@suse.de>
> > > Sent: Tuesday, October 5, 2021 4:12 PM
> > > To: Kailang <kailang@realtek.com>
> > > Cc: (alsa-devel@alsa-project.org) <alsa-devel@alsa-project.org>
> > > Subject: Re: ALC236 recording issue
> > >
> > > On Tue, 05 Oct 2021 08:55:14 +0200,
> > > Kailang wrote:
> > > >
> > > > Hi Takashi,
> > > >
> > > > Attach patch will solve alc236 recording issue for HP platform.
> > > >
> > > > Many Thanks.
> > > >
> > > > BR,
> > > > Kailang
> > >
> > > Applied now. Thanks.
> > >
> > >
> > > Takashi
> > > ------Please consider the environment before printing this e-mail.
> >
prev parent reply other threads:[~2021-10-07 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 6:55 ALC236 recording issue Kailang
2021-10-05 8:11 ` Takashi Iwai
2021-10-06 9:14 ` Kailang
2021-10-06 10:44 ` Takashi Iwai
2021-10-07 6:15 ` Kailang [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=294ba24e55ba40bc83a00a4f24e8c779@realtek.com \
--to=kailang@realtek.com \
--cc=alsa-devel@alsa-project.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