netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: alan-jenkins@tuffmail.co.uk
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	a.beregalov@gmail.com
Subject: Re: [PATCH] 8139cp: fix duplicate loglevel in module load message
Date: Tue, 22 Sep 2009 14:25:56 -0700 (PDT)	[thread overview]
Message-ID: <20090922.142556.76384742.davem@davemloft.net> (raw)
In-Reply-To: <4AB8D9B3.4010805@tuffmail.co.uk>

From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Date: Tue, 22 Sep 2009 15:05:39 +0100

> This was introduced by b93d58 "8139*: convert printk() to pr_<foo>()":
> 
> [ 2256252443 ] <6>8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
> 
> The "version" string is printed using pr_info(), so it doesn't need to
> include a loglevel.
> 
> Signed-off-by: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
> CC: Alexander Beregalov <a.beregalov@gmail.com>

Applied.

      reply	other threads:[~2009-09-22 21:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 14:05 [PATCH] 8139cp: fix duplicate loglevel in module load message Alan Jenkins
2009-09-22 21:25 ` 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=20090922.142556.76384742.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=a.beregalov@gmail.com \
    --cc=alan-jenkins@tuffmail.co.uk \
    --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).