From: Joe Perches <joe@perches.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: ipv4: Standardize prefixes for message logging
Date: Mon, 19 Mar 2012 14:14:47 -0700 [thread overview]
Message-ID: <1332191687.6525.15.camel@joe2Laptop> (raw)
In-Reply-To: <20120319.170349.957038489849471796.davem@davemloft.net>
On Mon, 2012-03-19 at 17:03 -0400, David Miller wrote:
> From: Joe Perches <joe@perches.com>
> Date: Mon, 19 Mar 2012 14:00:04 -0700
[]
> > Would you still take a similar IPv6: prefix
> > change for net-next or should I wait until
> > the next release cycle?
> Sure why not,
[]
> Instead, it really means "too late."
No worries, I'll set a good example instead.
prev parent reply other threads:[~2012-03-19 21:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 4:36 [PATCH net-next] net: Convert printks to pr_<level> Joe Perches
2012-03-12 6:48 ` David Miller
2012-03-12 17:03 ` [PATCH net-next] net: ipv4: Standardize prefixes for message logging Joe Perches
2012-03-13 0:05 ` David Miller
2012-03-13 0:35 ` Joe Perches
2012-03-19 21:00 ` Joe Perches
2012-03-19 21:03 ` David Miller
2012-03-19 21:14 ` Joe Perches [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=1332191687.6525.15.camel@joe2Laptop \
--to=joe@perches.com \
--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;
as well as URLs for NNTP newsgroup(s).