From: David Miller <davem@davemloft.net>
To: macro@linux-mips.org
Cc: hartleys@visionengravers.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] drivers/net/defxx.c: use %pM to show MAC address
Date: Mon, 04 Jan 2010 11:03:26 -0800 (PST) [thread overview]
Message-ID: <20100104.110326.161162074.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LFD.2.00.1001041833560.13474@eddie.linux-mips.org>
From: "Maciej W. Rozycki" <macro@linux-mips.org>
Date: Mon, 4 Jan 2010 18:49:48 +0000 (GMT)
> Nack. While I appreciate your effort, the FDDI standard defines opposite
> bit-ordering for MAC addresses written in the dash-separated and the
> colon-separated hexadecimal notation, which makes your change invalid,
> sorry (you'd have to bit-swap them too and that would make addresses
> counter-intuitive). Please note that `ifconfig' consistently uses the
> dash-separated notation for FDDI interfaces too (I haven't checked other
> tools like those in the "iproute" package; they may be buggy).
Well:
1) It's a bootup kernel message, we can use whatever format
we want.
2) As for consistency's sake, the only other FDDI driver using
alloc_fddidev() and friends, skfp, uses yet another format
for printing FDDI addresses to the log:
pr_debug(KERN_INFO "HW-Addr: %02x %02x %02x %02x %02x %02x\n",
So striving for "consistency" is a bit of a stretch.
Against a userspace tool's output format? Even more so...
And I doubt anybody is going to suddenly faint and become
confused if they see the MAC address in ethernet format.
In fact I'd rather see all of our FDDI drivers use the standard
ethernet MAC format in visible kernel log messages and save all
of that object code space that gets taken up by these by-hand
printk's in these obscure drivers.
next prev parent reply other threads:[~2010-01-04 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 18:28 H Hartley Sweeten
2010-01-04 18:49 ` Maciej W. Rozycki
2010-01-04 19:03 ` David Miller [this message]
2010-01-04 23:43 ` Maciej W. Rozycki
2010-01-05 1:05 ` [RFC PATCH] lib/vsprintf.c: Add %pMF to for FDDI bit reversed dashed output Joe Perches
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=20100104.110326.161162074.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--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®