linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: "Ivo van Doorn" <ivdoorn@gmail.com>,
	rt2400-devel@lists.sourceforge.net,
	linux-wireless@vger.kernel.org,
	"Michael Büker" <m.bueker@berlin.de>,
	linux-kernel@vger.kernel.org, akpm <akpm@linux-foundation.org>
Subject: Re: [Rt2400-devel] [PATCH] wireless: rt2x00: fix driver menu indenting
Date: Wed, 5 Mar 2008 13:11:29 -0500	[thread overview]
Message-ID: <20080305181129.GA6663@tuxdriver.com> (raw)
In-Reply-To: <20080304220029.1f152f00.randy.dunlap@oracle.com>

On Tue, Mar 04, 2008 at 10:00:29PM -0800, Randy Dunlap wrote:
> On Sun, 10 Feb 2008 20:03:25 +0100 Ivo van Doorn wrote:
>=20
> > On Sunday 10 February 2008, Randy Dunlap wrote:
> > > On Sat, 9 Feb 2008 16:23:06 +0100 Michael B=FCker wrote:
> > >=20
> > > > 2) When selecting "Ralink driver support" (CONFIG_RT2X00), the =
accompanying=20
> > > > drivers (CONFIG_RT2400PCI, CONFIG_RT61PC, ...) appear unindente=
d. They should=20
> > > > be indented by four spaces.
> > >=20
> > > Yes, patch is below.
> > >=20
> > > ---
> > > From: Randy Dunlap <randy.dunlap@oracle.com>
> > >=20
> > > Michael B=FCker <m.bueker@berlin.de> reports that the RT2x00 driv=
ers
> > > are not indented as they should be, so use proper dependencies to=
 make
> > > them be indented as expected.
> > >=20
> > > Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> >=20
> > Ack-by: Ivo van Doorn <IvDoorn@gmail.com>
> >=20
> > ---
> > John,
> > Could you push this directly into wireless-2.6 and probably upstrea=
m as well.
> >=20
> > Thanks.
> >=20
> > Ivo
>=20
> John, do you have this patch queued somewhere?

It is in net-2.6.26.

commit 0d84d78db5bad848e385cbb1e4ae2ea1f5f27641
Author: Randy Dunlap <randy.dunlap@oracle.com>
Date:   Sun Feb 10 10:52:52 2008 -0800

    wireless: rt2x00: fix driver menu indenting

    Michael B=FCker <m.bueker@berlin.de> reports that the RT2x00 driver=
s
    are not indented as they should be, so use proper dependencies to m=
ake
    them be indented as expected.

    Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
    Ack-by: Ivo van Doorn <IvDoorn@gmail.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>

Hth!

John
--=20
John W. Linville
linville@tuxdriver.com
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2008-03-05 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200802091623.06504.m.bueker@berlin.de>
2008-02-10 18:52 ` [PATCH] wireless: rt2x00: fix driver menu indenting Randy Dunlap
2008-02-10 19:03   ` [Rt2400-devel] " Ivo van Doorn
2008-03-05  6:00     ` Randy Dunlap
2008-03-05 18:11       ` 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=20080305181129.GA6663@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=akpm@linux-foundation.org \
    --cc=ivdoorn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=m.bueker@berlin.de \
    --cc=randy.dunlap@oracle.com \
    --cc=rt2400-devel@lists.sourceforge.net \
    /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).