linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: Pavel Roskin <proski@gnu.org>,
	mickflemm@gmail.com, linux-wireless@vger.kernel.org,
	stable@kernel.org, linville@tuxdriver.com,
	ath5k-devel@venema.h4ckr.net
Subject: Re: [stable] [PATCH] ath5k: don't enable MSI, we cannot handle it yet
Date: Fri, 18 Jul 2008 13:48:46 -0700	[thread overview]
Message-ID: <20080718204846.GA3181@kroah.com> (raw)
In-Reply-To: <200807181849.25320.mb@bu3sch.de>

On Fri, Jul 18, 2008 at 06:49:24PM +0200, Michael Buesch wrote:
> On Friday 18 July 2008 18:44:47 Pavel Roskin wrote:
> > On Fri, 2008-07-18 at 12:28 -0400, Pavel Roskin wrote:
> > > This fixes support for AR5006 chipset, which supports MSI
> > 
> > Sorry, I found Documentation/stable_kernel_rules.txt minutes after
> > sending the patch.  We need to get it to the Linus' tree first, then to
> > the stable tree.  I hope it won't take long.
> > 
> > To preempt possible questions: MSI is a nice thing, but we cannot enable
> > it without changing the interrupt handler.  If we do it, we break MSI
> > capable hardware.
> 
> Please include this into the patch changelog. It's highly confusing otherwise ;)

I agree.

Also, to get stuff into -stable easily, just add:
	Cc: stable <stable@kernel.org>
to the signed-off-by area in the patch and then when it goes into
Linus's tree, it will automatically be sent to us for inclusion.

Much easier on you and everyone else that way.

thanks,

greg k-h

      parent reply	other threads:[~2008-07-18 21:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 16:28 [PATCH] ath5k: don't enable MSI, we cannot handle it yet Pavel Roskin
2008-07-18 16:44 ` Pavel Roskin
2008-07-18 16:49   ` Michael Buesch
2008-07-18 16:56     ` [PATCH v2] " Pavel Roskin
2008-07-18 17:57       ` Nick Kossifidis
2008-07-18 18:29         ` Henrique de Moraes Holschuh
2008-07-18 23:38         ` Kyle McMartin
2008-07-18 20:48     ` Greg KH [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=20080718204846.GA3181@kroah.com \
    --to=greg@kroah.com \
    --cc=ath5k-devel@venema.h4ckr.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --cc=mickflemm@gmail.com \
    --cc=proski@gnu.org \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).