From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: netdev@vger.kernel.org, bhutchings@solarflare.com
Subject: Re: [RFC PATCH net-next 0/7] Add netdev_printk and netif_printk macros
Date: Fri, 12 Feb 2010 20:40:44 -0800 (PST) [thread overview]
Message-ID: <20100212.204044.38063904.davem@davemloft.net> (raw)
In-Reply-To: <1266034336.14805.84.camel@Joe-Laptop>
From: Joe Perches <joe@perches.com>
Date: Fri, 12 Feb 2010 20:12:16 -0800
> If you want to take the RFC patches, OK, but I could send
> a patchset that compiles all cases cleanly. Want that?
I've already fixed things up (by changing the arg in these macros to
"__dev") and pushed it out to net-next-2.6
next prev parent reply other threads:[~2010-02-13 4:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 21:49 [RFC PATCH net-next 0/7] Add netdev_printk and netif_printk macros Joe Perches
2010-02-09 21:49 ` [RFC PATCH net-next 1/7] netdevice.h: Add netdev_printk helpers like dev_printk Joe Perches
2010-02-09 21:49 ` [RFC PATCH net-next 2/7] drivers/net/atl1e: Use netdev_printk helpers Joe Perches
2010-02-09 21:49 ` [RFC PATCH net-next 3/7] include/linux/netdevice.h: Add netif_printk helpers Joe Perches
2010-02-09 21:49 ` [RFC PATCH net-next 4/7] drivers/net/r8196.c: Use netif_printk macros Joe Perches
2010-02-09 21:49 ` [RFC PATCH net-next 5/7] drivers/net/jme: Use netif_printk helpers Joe Perches
2010-02-09 21:49 ` [RFC PATCH net-next 6/7] drivers/net/qlge: " Joe Perches
2010-02-09 21:49 ` [RFC PATCH net-next 7/7] drivers/net/skge.c: Use netif_printk macros Joe Perches
2010-02-12 20:31 ` [RFC PATCH net-next 0/7] Add netdev_printk and " David Miller
2010-02-12 21:10 ` David Miller
2010-02-13 4:12 ` Joe Perches
2010-02-13 4:40 ` David Miller [this message]
2010-02-15 0:47 ` [PATCH net-next] niu.c: Use pr_<level>, netdev_<level> and netif_<level> macros Joe Perches
2010-02-15 6:41 ` David Miller
2010-02-15 8:13 ` David Miller
2010-02-15 8:23 ` Joe Perches
2010-02-15 8:30 ` David Miller
2010-02-15 8:40 ` 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=20100212.204044.38063904.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=joe@perches.com \
--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).