All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: "John W. Linville" <linville@tuxdriver.com>,
	netdev@vger.kernel.org, Roel Kluin <roel.kluin@gmail.com>,
	libertas-dev@lists.infradead.org
Subject: Re: [PATCH] libertas: name the network device wlan%d
Date: Wed, 12 Aug 2009 10:55:46 +0200	[thread overview]
Message-ID: <20090812085546.GA9464@buzzloop.caiaq.de> (raw)
In-Reply-To: <20090812075624.GC18186@guralp.com>

On Wed, Aug 12, 2009 at 08:56:24AM +0100, Bob Dunlop wrote:
> > > 
> > > Fix this by calling it wlan%d.
> > > 
> > I'm fine with changing it, but it isn't really wrong either -- it's
> > just a name, and afterall in most cases all the user will see is
> > ethernet frames.
> > 
> > Comments from the libertas driver crew?
> 
> Well I've been applying the equivalent of this patch privately since
> we started using the libertas driver.  We build systems with one or two
> wired Ethernets and then an optional wireless module.
> 
> A fixed name wlan0 is a lot easier than explaining to a user that the
> interface might be eth1 or eth2 depending on which model they have, or
> that eth1 might be wired or wireless.  It also simplifies scripts and
> configuration file handling.
> 
> I'm sure there are many other solutions for big systems but this is
> really simple for small boys.

Yes, our story here is very similar :)


  reply	other threads:[~2009-08-12  8:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 14:13 [PATCH] libertas: name the network device wlan%d Daniel Mack
2009-08-11 14:34 ` John W. Linville
2009-08-12  7:56   ` Bob Dunlop
2009-08-12  8:55     ` Daniel Mack [this message]
2009-08-12 16:31   ` Dan Williams
2009-08-13  3:48     ` Daniel Drake
2009-08-13 17:28       ` Dan Williams
     [not found] ` <20090811151051.GA18186@guralp.com>
2009-08-11 15:33   ` Daniel Mack

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=20090812085546.GA9464@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=roel.kluin@gmail.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 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.