From: "Eilon Greenstein" <eilong@broadcom.com>
To: "Joe Perches" <joe@perches.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 2/2] bnx2x: Coalesce pr_cont uses and fix DP typos
Date: Tue, 9 Aug 2011 17:41:23 +0300 [thread overview]
Message-ID: <1312900883.31417.2.camel@lb-tlvb-eilong.il.broadcom.com> (raw)
In-Reply-To: <98d09e1b3d7a73bf5f2744f0ca238321573e4579.1312818707.git.joe@perches.com>
On Mon, 2011-08-08 at 08:53 -0700, Joe Perches wrote:
> Uses of pr_cont should be avoided where reasonably possible
> because they can be interleaved by other threads and processes.
>
> Coalesce pr_cont uses.
>
> Fix typos, duplicated words and spacing in DP uses caused
> by split multi-line formats. Coalesce some of these
> split formats. Add missing terminating newlines to DP uses.
>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
....
> @@ -12254,7 +12261,7 @@ void bnx2x_period_func(struct link_params *params, struct link_vars *vars)
> {
> struct bnx2x *bp = params->bp;
> if (!params) {
> - DP(NETIF_MSG_LINK, "Ininitliazed params !\n");
> + DP(NETIF_MSG_LINK, "Uninitialized params !\n");
> return;
> }
> /* DP(NETIF_MSG_LINK, "Periodic called vars->phy_flags 0x%x speed 0x%x
This does not apply on the current net-next. Other than that - it looks
good.
Please re-submit this patch series once net-next is opened for driver
changes (see: http://marc.info/?l=linux-netdev&m=131278578427946&w=2 )
and I will ACK it.
Thanks,
Eilon
prev parent reply other threads:[~2011-08-09 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 15:53 [PATCH net-next 0/2] bnx2x: Logging message cleanups Joe Perches
2011-08-08 15:53 ` [PATCH net-next 1/2] bnx2x: Remove local defines for %pM and mac address Joe Perches
2011-08-08 15:53 ` [PATCH net-next 2/2] bnx2x: Coalesce pr_cont uses and fix DP typos Joe Perches
2011-08-09 14:41 ` Eilon Greenstein [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=1312900883.31417.2.camel@lb-tlvb-eilong.il.broadcom.com \
--to=eilong@broadcom.com \
--cc=joe@perches.com \
--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®