From: David Miller <davem@davemloft.net>
To: mikpe@it.uu.se
Cc: joe@perches.com, netdev@vger.kernel.org,
grundler@parisc-linux.org, kyle@mcmartin.ca,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/net/tulip/eeprom.c: fix bogus "(null)" in tulip init messages
Date: Sat, 13 Mar 2010 12:26:31 -0800 (PST) [thread overview]
Message-ID: <20100313.122631.129768465.davem@davemloft.net> (raw)
In-Reply-To: <19351.61461.545790.609086@pilspetsen.it.uu.se>
From: Mikael Pettersson <mikpe@it.uu.se>
Date: Wed, 10 Mar 2010 20:16:37 +0100
> Joe Perches writes:
> > Signed-off-by: Joe Perches <joe@perches.com>
...
> Tested-by: Mikael Pettersson <mikpe@it.uu.se>
Applied, thanks everyone.
prev parent reply other threads:[~2010-03-13 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 15:33 [BUG 2.6.34-rc1] bogus "(null)" in tulip init messages Mikael Pettersson
2010-03-10 16:41 ` David Miller
2010-03-10 17:34 ` [PATCH] drivers/net/tulip/eeprom.c: fix " Joe Perches
2010-03-10 19:16 ` Mikael Pettersson
2010-03-13 20:26 ` David Miller [this message]
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=20100313.122631.129768465.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=grundler@parisc-linux.org \
--cc=joe@perches.com \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--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;
as well as URLs for NNTP newsgroup(s).