linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Andrew Price <andy@andrewprice.me.uk>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rt2x00: Fix radio LED type check
Date: Thu, 8 Jan 2009 19:49:43 +0100	[thread overview]
Message-ID: <200901081949.43463.IvDoorn@gmail.com> (raw)
In-Reply-To: <20090108181035.GA27377@silver.sucs.org>

On Thursday 08 January 2009, 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 had added John to the CC list in my initial reply to notify him of the patch,
he will pick up the patch and make sure it will make its way to Linus. :)

Ivo

  reply	other threads:[~2009-01-08 18:49 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 [this message]
2009-01-08 18:50     ` John W. Linville

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=200901081949.43463.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=andy@andrewprice.me.uk \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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).