All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: driverdevel <devel@driverdev.osuosl.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Missed Cc for stable
Date: Mon, 23 Apr 2012 14:33:35 -0700	[thread overview]
Message-ID: <20120423213335.GA3603@kroah.com> (raw)
In-Reply-To: <4F92F910.60900@lwfinger.net>

On Sat, Apr 21, 2012 at 01:14:40PM -0500, Larry Finger wrote:
> Greg,
> 
> I missed a Cc for stable in this patch:
> 
> ================================================
> commit 2080913e017ab9f88379d93fd09546ad95faf87b
> Author: Larry Finger <Larry.Finger@lwfinger.net>
> Date:   Sat Feb 25 18:10:21 2012 -0600
> 
>     staging: r8712u: Fix regression caused by commit 8c213fa
> 
>     In commit 8c213fa "staging: r8712u: Use asynchronous firmware loading",
>     the command to release the firmware was placed in the wrong routine.
> 
>     In combination with the bug introduced in commit a5ee652 "staging: r8712u:
>     Interface-state not fully tracked", the driver attempts to upload firmware
>     that had already been released. This bug is the source of one of the
>     problems in https://bugs.archlinux.org/task/27996#comment89833.
> 
>     Tested-by: Alberto Lago Ballesteros <saniukeokusainaya@gmail.com>
>     Tested-by: Adrian <agib@gmx.de>
>     Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
>     Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ==============================================

Now applied to the 3.3-stable tree.

thanks,

greg k-h

      reply	other threads:[~2012-04-23 21:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-21 18:14 Missed Cc for stable Larry Finger
2012-04-23 21:33 ` Greg Kroah-Hartman [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=20120423213335.GA3603@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@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 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.