From: Sakari Ailus <sakari.ailus@iki.fi>
To: Joe Perches <joe@perches.com>
Cc: netdev@vger.kernel.org, Samuel Chessman <chessman@tux.org>
Subject: Re: [PATCH] tlan: Use pr_fmt, pr_<level> and netdev_<level>, remove changelog
Date: Mon, 24 Jan 2011 23:54:50 +0200 [thread overview]
Message-ID: <4D3DF52A.50705@iki.fi> (raw)
In-Reply-To: <1295644161.25868.35.camel@Joe-Laptop>
Joe Perches wrote:
> On Fri, 2011-01-21 at 22:49 +0200, Sakari Ailus wrote:
>> Joe Perches wrote:
>>> Neatening and standardization to the standard logging mechanisms.
>>> The changelog isn't useful anymore.
>>> Miscellaneous speen/speed typo correction.
>> I definitely think it's good to replace pr_ prints with netdev_* macros.
> []
>> I think these prints could be removed by a separate patch before this
>> one. Would you like to do that, or shall I? :-)
>
> Hi.
Hi Joe,
> Why don't you pick and choose the parts you think appropriate,
> convert the stuff you think should be converted and submit it
> as you think best.
>
> There's no need to wait for me to do it or attribute it to me.
I'll incorporate your patch to a tlan patchset. Thanks.
Regards,
--
Sakari Ailus
sakari.ailus@iki.fi
prev parent reply other threads:[~2011-01-24 21:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 18:49 [PATCH 0/3] tlan improvements Sakari Ailus
2011-01-06 18:50 ` [PATCH 1/3] tlan: Code cleanup: checkpatch.pl is relatively happy now Sakari Ailus
2011-01-06 18:50 ` [PATCH 2/3] tlan: Fix partner capability printout Sakari Ailus
2011-01-06 18:50 ` [PATCH 3/3] tlan: add suspend/resume support Sakari Ailus
2011-01-06 19:22 ` [PATCH 2/3] tlan: Fix partner capability printout Ben Hutchings
2011-01-06 19:36 ` Sakari Ailus
2011-01-06 19:44 ` Ben Hutchings
2011-01-06 22:48 ` [PATCH] tlan: Use pr_fmt, pr_<level> and netdev_<level>, remove changelog Joe Perches
2011-01-10 7:39 ` David Miller
2011-01-13 6:19 ` Sakari Ailus
2011-01-21 20:49 ` Sakari Ailus
2011-01-21 21:09 ` Joe Perches
2011-01-24 21:54 ` Sakari Ailus [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=4D3DF52A.50705@iki.fi \
--to=sakari.ailus@iki.fi \
--cc=chessman@tux.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.