From: David Miller <davem@davemloft.net>
To: nhorman@tuxdriver.com
Cc: netdev@vger.kernel.org, romieu@fr.zoreil.com, brandon@ifup.org
Subject: Re: [PATCH] r8169: clean up my printk uglyness
Date: Thu, 01 Apr 2010 19:33:21 -0700 (PDT) [thread overview]
Message-ID: <20100401.193321.257691706.davem@davemloft.net> (raw)
In-Reply-To: <20100401173007.GC14069@shamino.rdu.redhat.com>
From: Neil Horman <nhorman@tuxdriver.com>
Date: Thu, 1 Apr 2010 13:30:07 -0400
> On Thu, Apr 01, 2010 at 10:53:56AM -0400, Neil Horman wrote:
>> Fix formatting on r8169 printk
>>
>> Brandon Philips noted that I had a spacing issue in my printk for the last r8169
>> patch that made it quite ugly. Fix that up and add the PFX macro to it as well
>> so it looks like the other r8169 printks
>>
>> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
>>
>>
> Grr, yes thanks, V2, fixing my idiocy :)
>
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
Applied, thanks Neil.
prev parent reply other threads:[~2010-04-02 2:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 14:53 [PATCH] r8169: clean up my printk uglyness Neil Horman
2010-04-01 17:30 ` Neil Horman
2010-04-02 2:33 ` David Miller [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=20100401.193321.257691706.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brandon@ifup.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=romieu@fr.zoreil.com \
/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).