All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] drivers/net/ne3210.c: cleanups
Date: Fri, 25 Feb 2005 01:00:37 +0100	[thread overview]
Message-ID: <20050225000037.GG8651@stusta.de> (raw)
In-Reply-To: <421A471A.7090503@pobox.com>

On Mon, Feb 21, 2005 at 03:39:54PM -0500, Jeff Garzik wrote:
> Adrian Bunk wrote:
> >@@ -197,7 +194,7 @@
> > 	ei_status.priv = phys_mem;
> > 
> > 	if (ei_debug > 0)
> >-		printk(version);
> >+		printk("ne3210 driver");
> 
> 
> missing newline.  Do something like "ns3210 __DATE__ loaded.\n"
> 
> Ditto for seeq8002.

Sorry for the missing newline.

I have to admit I still don't see why these printk's have to stay:
In both files, there are other printk's nearby that print the name of 
the driver.

__DATE__ doesn't provide any information that wasn't already available 
in the first line of the dmesg output.

> 	Jeff

cu
Adrian

--

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-02-25  0:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-18 23:46 [2.6 patch] drivers/net/ne3210.c: cleanups Adrian Bunk
2005-02-21  1:40 ` Jeff Garzik
2005-02-21 14:48   ` Adrian Bunk
2005-02-21 20:39     ` Jeff Garzik
2005-02-25  0:00       ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-19  0:36 Adrian Bunk
2005-05-02  1:46 Adrian Bunk
2005-05-30 20:56 Adrian Bunk
2005-06-24 20:09 Adrian Bunk
2005-06-24 20:36 ` Jean Delvare

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=20050225000037.GG8651@stusta.de \
    --to=bunk@stusta.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@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.