linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Filipus Klutiero <chealer@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: rt2400-devel@lists.sourceforge.net
Subject: Re: [Rt2400-devel] rt2x00: cleanup Kconfig help
Date: Sun, 20 Apr 2008 14:20:00 -0400	[thread overview]
Message-ID: <200804201420.00215.chealer@gmail.com> (raw)
In-Reply-To: <200804141333.33128.IvDoorn@gmail.com>

Le April 14, 2008 07:33:32 am Ivo van Doorn, vous avez =E9crit=A0:
> > > >  	  When compiled as a module, this driver will be called
> > > > "rt2500usb.ko".
> > > >
> > > >  config RT73USB
> > > > -	tristate "Ralink rt73 usb support"
> > > > +	tristate "Ralink RT2571W and RT2671 (USB) support"
> > > >  	depends on RT2X00 && USB
> > > >  	select RT2X00_LIB_USB
> > > >  	select RT2X00_LIB_FIRMWARE
> > > >  	---help---
> > > > -	  This is an experimental driver for the Ralink rt73 wireless=
 chip.
> > > > +	  This is an experimental driver for the RT2571W and RT2671 M=
AC/BBP
> > > > chips. It supports Ralink RT2501USB and RT5201USB wireless chip=
sets.
> > > > When compiled as a module, this driver will be called "rt73usb.=
ko".
> > >
> > > *sigh* you seem to be absolutely sure you want to break any form =
of
> > > consistency in the rt2x00 KConfig entry. So to show how I would l=
ike to
> > > see it I have the following patch. Unless you have objections aga=
inst
> > > below changes I will push this forward.
> >
> > No objection, but note that:
> > * this has both "hardware that feature*s*" and  "hardware that feat=
ure"
>
> I'll fix that.
>
> > * The names of drivers are duplicated and not exactly the same. For
> > example, "This is the experimental rt2500pci driver [...]" vs "[...=
] this
> > driver will be called "rt2500pci.ko"".
>
> I'll change that to:
> This is the experimental rt2500pci driver [...]" vs "[...] the module=
 will
> be called "rt2500pci.ko"".
>
> > Here is the third version of my patch.
>
> NACK
>
> All my complaints about your previous patch still aplies to this new =
one,
> and I am not going to repeat myself over and over again for exactly t=
he
> same.
Certainly not; my last update was specifically to address some of your=20
complaints. Which one(s) did I forget to address?
>
> As for the bug this patch is supposedly going to fix,
> the config option is named:
> 	tristate "Ralink rt2500 usb support"
> How can people confuse that with pci support?
> =DDour patch suggests the confusion is to blame because there is a sp=
ace
> between rt2500 and usb, and that usb isn't capitalized...
It's the text quoted in the bug report which *might* be confusing. Lack=
 of=20
capitalization isn't going to confuse anyone, of course.
--
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-04-20 18:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12 19:09 rt2x00: cleanup Kconfig help Filipus Klutiero
2008-04-12 19:28 ` Ivo van Doorn
2008-04-12 20:10   ` Filipus Klutiero
2008-04-12 20:53     ` [Rt2400-devel] " Ivo van Doorn
2008-04-12 22:17       ` Filipus Klutiero
2008-04-13 10:44         ` Ivo van Doorn
2008-04-14  6:36           ` Filipus Klutiero
2008-04-14 11:33             ` Ivo van Doorn
2008-04-20 18:20               ` Filipus Klutiero [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=200804201420.00215.chealer@gmail.com \
    --to=chealer@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --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).