All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Andrew Price <andy@andrewprice.me.uk>
Cc: Ivo Van Doorn <ivdoorn@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rt2x00: Fix radio LED type check
Date: Thu, 8 Jan 2009 13:50:47 -0500	[thread overview]
Message-ID: <20090108185047.GC3861@tuxdriver.com> (raw)
In-Reply-To: <20090108181035.GA27377@silver.sucs.org>

On Thu, Jan 08, 2009 at 06:10:35PM +0000, Andrew Price wrote:
> On Fri, Jan 02, 2009 at 12:14:17PM +0100, Ivo Van Doorn wrote:
> > On Fri, Jan 2, 2009 at 9:05 AM, Andrew Price <andy@andrewprice.me.uk> wrote:
> > > Since commit 9a95dba32735534bda59def40c747bf606fedf05 "rt2x00: Fix LED
> > > state handling", rt2x00leds_led_radio wrongly checks that the LED type
> > > is LED_TYPE_ASSOC. This patch makes it check for LED_TYPE_RADIO once
> > > again.
> > >
> > > Signed-off-by: Andrew Price <andy@andrewprice.me.uk>
> > 
> > Good catch. Thanks.
> > 
> > Acked-by: Ivo van Doorn <IvDoorn@gmail.com>
> 
> Thanks for that. I'm a little new to this so I'm not sure what happens now.
> Will the patch go into John's tree and make it's way to Linus' tree (where the
> bug is) or should I send it directly to Linus/LKML with Ivo's Acked-by line?

I've got it, thanks.

John
-- 
John W. Linville		Linux should be at the core
linville@tuxdriver.com			of your literate lifestyle.

      parent reply	other threads:[~2009-01-08 19:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-02  8:05 [PATCH] rt2x00: Fix radio LED type check Andrew Price
2009-01-02 11:14 ` Ivo Van Doorn
2009-01-02 14:10   ` Marcel Holtmann
2009-01-02 14:21     ` Ivo van Doorn
2009-01-08 18:10   ` Andrew Price
2009-01-08 18:49     ` Ivo van Doorn
2009-01-08 18:50     ` John W. Linville [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=20090108185047.GC3861@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=andy@andrewprice.me.uk \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@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.