Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: stable@vger.kernel.org
Subject: Re: Missing stable backports for sound/*
Date: Sat, 11 Jul 2015 07:38:35 -0700	[thread overview]
Message-ID: <20150711143835.GA3880@kroah.com> (raw)
In-Reply-To: <s5h4mlb2kok.wl-tiwai@suse.de>

On Sat, Jul 11, 2015 at 09:54:51AM +0200, Takashi Iwai wrote:
> Hi Greg,
> 
> it seems that the whole bunch of stable fixes in sound/* are missing
> in the recent stable releases.  Could you add them for the next stable
> release?
> 
> Below are the commits I grep'ed via v4.1..HEAD sound/*:
> 
> 14ba3ec1de043260cecd9e828ea2e3a0ad302893
> ebb6ad73e645b8f2d098dd3c41d2ff0da4146a02
> 12c350050538c7dc779c083b7342bfd20f74949c
> 0b51601d4504f46f585eed823485101390f0b588
> 15575ed544910464715df5c45a44b9732e415b93
> 80ba2669ec8c3e6517aa935001f6cb8809bf3df4
> 1cf0f44811b754b64283b11ef0e60cb0de07b29c
> 7ea3470a7277380248135a592a849e1c27960b2f
> a077e81ec61e07a7f86997d045109f06719fbffe
> 60b93030b44a8c2cd015cebe5624fd7552ec67ec
> ec56af67a10a0d82b79027878a81fce08d002d50
> 735c75cf4d434862e38c01dcfb2ce8d2fcb9035f
> 650474fb737c3e0ea0f6ab8e43c2cd161080ce5c
> 831bfdf9520e389357cfeee42a6174a73ce7bdb7
> 7819717b11346b8a5420b223b46600e394049c66
> 4df3fd1700abbb53bd874143dfd1f9ac9e7cbf4b
> 4275554dccdf0afac07b2b638ba7456095629558
> 

I still have over 200 patches to go apply to the stable tree that have
been marked for inclusion by the maintainers, so give me a chance to go
through them first :)

After that I'll take this list of git commits and see if I've missed
anything.

thanks,

greg k-h

  reply	other threads:[~2015-07-11 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-11  7:54 Missing stable backports for sound/* Takashi Iwai
2015-07-11 14:38 ` Greg KH [this message]
2015-07-11 18:56   ` 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=20150711143835.GA3880@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.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