From: Greg KH <gregkh@linuxfoundation.org>
To: Ju Hyung Park <qkrwngud825@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/2] ALSA: hda - Turn CX8200 into D3 as well upon reboot
Date: Sat, 18 Aug 2018 16:38:00 +0200 [thread overview]
Message-ID: <20180818143800.GA670@kroah.com> (raw)
In-Reply-To: <CAD14+f1Yf-RpaLENsUC73AF9T=a_aOXzP9GaKt2ZVw58WXuBBQ@mail.gmail.com>
On Sat, Aug 18, 2018 at 11:29:11PM +0900, Ju Hyung Park wrote:
> Hi, Greg.
>
> I'd like to know if there's a reason on why these ALSA patches(2 in
> total) aren't brought to linux-stable yet.
What specific patches are you referring to here? I do not see anything
in this email :(
What is the git commit id in Linus's tree? What stable tree(s) do you
want them applied to?
> I see a lot of patches merged to linux-stable and stable-queue that
> are much newer than those patches.
>
> I'd appreciate it if you can merge those ASAP.
Have you read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly?
If not, please do so.
thanks,
greg k-h
next prev parent reply other threads:[~2018-08-18 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 18:16 [PATCH 1/2] ALSA: hda - Turn CX8200 into D3 as well upon reboot Park Ju Hyung
2018-07-28 16:58 ` Takashi Iwai
[not found] ` <CAD14+f30SuF=MJsXWcLg3RFrJOO32wdvDKPnb2mNfnqtGWqhDw@mail.gmail.com>
[not found] ` <s5hzhy6mdxn.wl-tiwai@suse.de>
[not found] ` <CAD14+f1VoGpOUHT6Jn_D_Svsg6MZ6e1X1gDTNoYX9_CbaVQg6w@mail.gmail.com>
[not found] ` <s5hwotamdo7.wl-tiwai@suse.de>
[not found] ` <CAD14+f3qrhVNT0hq77fE7ADhXbzSLm1R5r_mv6rLyuhJHPXs=w@mail.gmail.com>
[not found] ` <s5hy3d4itgj.wl-tiwai@suse.de>
2018-08-18 14:29 ` Ju Hyung Park
2018-08-18 14:38 ` Greg KH [this message]
[not found] ` <CAD14+f1K=s5bk0SQJ3s4rhg=jGhdpp_MR9XyZ-T7=jmthzot4Q@mail.gmail.com>
2018-08-18 16:56 ` Fwd: " Ju Hyung Park
2018-08-19 6:09 ` Greg KH
[not found] ` <CAD14+f0QASSwkTuMEKrEAg217HM--HdcrPF7UDHF6RuPoAo89g@mail.gmail.com>
2018-08-18 16:56 ` Ju Hyung Park
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=20180818143800.GA670@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=qkrwngud825@gmail.com \
--cc=stable@vger.kernel.org \
/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