mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Christian Kujau <lists@nerdbynature.de>
Cc: linux-kernel@vger.kernel.org,
	linux1394-devel@lists.sourceforge.net,
	linux-hotplug@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as interface name
Date: Sun, 24 May 2009 11:47:04 +0200 (CEST)	[thread overview]
Message-ID: <tkrat.6c3758bf0544a790@s5r6.in-berlin.de> (raw)
In-Reply-To: <alpine.DEB.2.01.0905232309400.7424@bogon>

Christian Kujau wrote at LKML:
> If the patch will be accepted at all and it's not too late to ask: I'd 
> vote for fw%d as well, "firefire" just looks too long, for me at least. 

I think I'll leave the driver as it is.
As I just noticed, we would lose interface renaming by udev.
>From udev/extras/rule_generator/75-persistent-net-generator.rules:

  # device name whitelist
  KERNEL!="eth*|ath*|wlan*[0-9]|msh*|ra*|sta*|ctc*|lcs*|hsi*", GOTO="persistent_net_generator_end"

Besides, if we can we should avoid fw%d because this will clash with
udev rules which match KERNEL=="fw*", as in
udev/rules/redhat/40-redhat.rules.
-- 
Stefan Richter
-=====-==--= -=-= ==---
http://arcgraph.de/sr/


  reply	other threads:[~2009-05-24  9:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21 13:29 Stefan Richter
2009-05-21 13:48 ` Jiri Pirko
2009-05-21 14:31   ` Stefan Richter
2009-05-21 16:43     ` Kay Sievers
2009-05-24  6:13     ` Christian Kujau
2009-05-24  9:47       ` Stefan Richter [this message]
2009-05-25  8:33         ` Matthias Schwarzott
2009-05-25 10:43           ` Stefan Richter
2009-05-25 10:57           ` Kay Sievers
2009-05-21 19:34 ` David Miller
2009-05-21 20:13   ` Stefan Richter
2009-05-21 20:33     ` David Miller
2009-05-21 21:35       ` Stefan Richter

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=tkrat.6c3758bf0544a790@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=linux-hotplug@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=lists@nerdbynature.de \
    --cc=netdev@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®