Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	USB mailing list <linux-usb@vger.kernel.org>,
	linux-pci@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Fix nomenclature for USB and PCI wireless devices
Date: Thu, 10 Aug 2023 11:32:53 +0200	[thread overview]
Message-ID: <c5c6d4f8e5151f8bc962dce39d776ab4bbaccb58.camel@sipsolutions.net> (raw)
In-Reply-To: <2023081059-omen-hence-c554@gregkh>

On Thu, 2023-08-10 at 11:31 +0200, Greg KH wrote:
> On Thu, Aug 10, 2023 at 11:29:57AM +0200, Johannes Berg wrote:
> > On Wed, 2023-08-09 at 10:05 -0400, Alan Stern wrote:
> > > On Wed, Aug 09, 2023 at 02:16:48PM +0200, Greg KH wrote:
> > > > On Tue, Aug 08, 2023 at 08:44:48PM -0400, Alan Stern wrote:
> > > > > A mouse that uses a USB connection is called a "USB mouse" device (or
> > > > > "USB mouse" for short), not a "mouse USB" device.  By analogy, a WiFi
> > > > > adapter that connects to the host computer via USB is a "USB wireless"
> > > > > device, not a "wireless USB" device.  (The latter term more properly
> > > > > refers to a defunct Wireless USB specification, which described a
> > > > > technology for sending USB protocol messages over an ultra wideband
> > > > > radio link.)
> > > > > 
> > > > > Similarly for a WiFi adapter card that plugs into a PCIe slot: It is a
> > > > > "PCIe wireless" device, not a "wireless PCIe" device.
> > > > > 
> > > > > Rephrase the text in the kernel source where the word ordering is
> > > > > wrong.
> > > > > 
> > > > > Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
> > > > 
> > > > Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > 
> > > Can you accept this patch, or should I ask Johannes Berg or Kalle Valo 
> > > to merge it through the wireless subsystem?
> > > 
> > 
> > Given that it touches pretty much only wireless drivers, I guess we
> > should take it? For -next, though, so since Kalle usually takes drivers
> > I'll wait for him to get back.
> > 
> > But the potential for conflicts seems low too, so I guess either way is
> > fine.
> 
> I provided my reviewed-by as I assumed it would go through the wireless
> or networking tree.  Otherwise, yes, I can take it, your choice.

We'll just take it, seems easier. The staging/eeepc is probably even
less likely to conflict.

johannes

  reply	other threads:[~2023-08-10 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09  0:44 [PATCH] Fix nomenclature for USB and PCI wireless devices Alan Stern
2023-08-09 12:16 ` Greg KH
2023-08-09 14:05   ` Alan Stern
2023-08-10  9:29     ` Johannes Berg
2023-08-10  9:31       ` Greg KH
2023-08-10  9:32         ` Johannes Berg [this message]
2023-08-25  9:57 ` Kalle Valo

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=c5c6d4f8e5151f8bc962dce39d776ab4bbaccb58.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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