From: Joe Perches <joe@perches.com>
To: David Dillow <dave@thedillows.org>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 14/15] drivers/net/typhoon.c: Use (pr|netdev)_<level> macro helpers
Date: Wed, 17 Feb 2010 19:11:43 -0800 [thread overview]
Message-ID: <1266462703.8446.237.camel@Joe-Laptop.home> (raw)
In-Reply-To: <1266462064.5719.78.camel@obelisk.thedillows.org>
On Wed, 2010-02-17 at 22:01 -0500, David Dillow wrote:
> I'm don't see how dropping the typhoon patch slows Joe down, so
> I'd like to avoid having to fix things up after the fact.
I think that all of these can use netdev_<level>.
Also, these patches are trivial and can be
applied at leisure.
I do them with the long-term goal of creating
consistent kernel logging mechanisms.
Might take decades.
Anyway, if it's applied now, it can be cleaned
up as you like eventually. Certainly it'd be
done before 2.6.34 is released in a few months.
cheers, Joe
next prev parent reply other threads:[~2010-02-18 3:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 1:01 [PATCH net-next 00/15] drivers/net: Use (pr|netdev|netif)_<level> macros Joe Perches
2010-02-18 1:01 ` [PATCH net-next 01/15] drivers/net/8139cp.c: Use (pr|netdev|netif)_<level> macro helpers Joe Perches
2010-02-18 1:01 ` [PATCH net-next 02/15] drivers/net/8139too.c: " Joe Perches
2010-02-18 1:01 ` [PATCH net-next 03/15] drivers/net/b44.c: " Joe Perches
2010-02-18 1:01 ` [PATCH net-next 04/15] drivers/net/bnx2.c: " Joe Perches
2010-02-18 1:01 ` [PATCH net-next 05/15] drivers/net/bnx2x: " Joe Perches
2010-02-18 1:01 ` [PATCH net-next 06/15] drivers/net/cassini.c: " Joe Perches
2010-02-18 1:01 ` [PATCH net-next 07/15] drivers/net/cnic.c: Use (pr|netdev)_<level> " Joe Perches
2010-02-18 1:01 ` [PATCH net-next 08/15] drivers/net/pci-skeleton.c: Use (pr|netdev|netif)_<level> " Joe Perches
2010-02-18 1:01 ` [PATCH net-next 09/15] drivers/net/sis190.c: " Joe Perches
2010-02-18 6:00 ` [PATCH V2 " Joe Perches
2010-02-18 23:44 ` David Miller
2010-02-18 1:01 ` [PATCH net-next 10/15] drivers/net/skge.c: Use (pr|netdev)_<level> " Joe Perches
2010-02-18 1:01 ` [PATCH net-next 11/15] " Joe Perches
2010-02-18 1:01 ` [PATCH net-next 12/15] drivers/net/sky2.c: " Joe Perches
2010-02-18 1:02 ` [PATCH net-next 13/15] drivers/net/tg3.c: " Joe Perches
2010-02-18 5:44 ` [PATCH V2 " Joe Perches
2010-02-18 23:44 ` David Miller
2010-02-18 1:02 ` [PATCH net-next 14/15] drivers/net/typhoon.c: " Joe Perches
2010-02-18 1:59 ` David Dillow
2010-02-18 2:18 ` Joe Perches
2010-02-18 2:30 ` David Dillow
2010-02-18 2:41 ` David Miller
2010-02-18 3:01 ` David Dillow
2010-02-18 3:10 ` David Miller
2010-02-18 3:22 ` David Dillow
2010-02-18 3:11 ` Joe Perches [this message]
2010-02-18 2:53 ` Joe Perches
2010-02-18 3:18 ` David Dillow
2010-02-18 1:02 ` [PATCH net-next 15/15] drivers/net/yellowfin.c: " Joe Perches
2010-02-18 1:46 ` [PATCH net-next 00/15] drivers/net: Use (pr|netdev|netif)_<level> macros David Miller
2010-02-18 2:00 ` David Dillow
2010-02-18 2:01 ` David Miller
2010-02-18 2:06 ` David Miller
2010-02-18 2:19 ` David Dillow
2010-02-18 2:20 ` 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=1266462703.8446.237.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=dave@thedillows.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.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®