From: Joe Perches <joe@perches.com>
To: Alexandru Gagniuc <mr.nuke.me@gmail.com>, netdev@vger.kernel.org
Cc: Roger Luethi <rl@hellgate.ch>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] via-rhine: Logging cleanups and use random MAC address
Date: Sat, 16 Apr 2011 17:15:24 -0700 [thread overview]
Message-ID: <cover.1302998994.git.joe@perches.com> (raw)
In-Reply-To: <4DAA12C0.7030106@gmail.com>
Alexandru's patch didn't apply so use the
current logging standards and fix the whitespace
in Alexandru's patch.
Joe Perches (2):
via_rhine: Use netdev_<level> and pr_<level>
via-rhine: Assign random MAC address if necessary
drivers/net/via-rhine.c | 240 ++++++++++++++++++++++-------------------------
1 files changed, 114 insertions(+), 126 deletions(-)
--
1.7.4.2.g597a6.dirty
next parent reply other threads:[~2011-04-17 0:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4DAA12C0.7030106@gmail.com>
2011-04-17 0:15 ` Joe Perches [this message]
2011-04-17 0:15 ` [PATCH 1/2] via_rhine: Use netdev_<level> and pr_<level> Joe Perches
2011-04-18 0:56 ` David Miller
2011-04-17 0:15 ` [PATCH 2/2] via-rhine: Assign random MAC address if necessary Joe Perches
2011-04-18 0:57 ` David Miller
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=cover.1302998994.git.joe@perches.com \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mr.nuke.me@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rl@hellgate.ch \
/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