public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Andrzej Krzysztofowicz <ankry@green.mif.pg.gda.pl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] some network __init code
Date: Mon, 23 Apr 2001 16:23:51 -0400	[thread overview]
Message-ID: <3AE48F57.2A859328@mandrakesoft.com> (raw)
In-Reply-To: <200104232015.WAA07001@green.mif.pg.gda.pl>

> 1. What are the char* -> char array conversions of "version" strings for ?

char*="blah" generates a char pointer variable, pointing to the constant
string "blah".  char[]="blah" eliminates the char pointer variable, so
the resulting code is [slightly] smaller.


> 3. The following patch
>    - marks most of the version strings __initdata/__devinitdata (necessary
>      removing of "const" from their declaration), removes unnecessary format
>      strings from their printk()s, moves to __init/adds log level markers to
>      them (KERN_*)
>    - adds/fixes some other __init code,
>    - removes some unnecessary zero initializers
>    from most of the network drivers.

looks ok at a glance, I will probably apply it after reviewing further.

note a further cleanup is to look at each driver, and make sure (a) it
-always- printk's version if -DMODULE, and (b) if only printk's version
if hardware is found, if not -DMODULE.  You can look at pci net drivers
in 2.4.4-pre6 for an example of how I did this.

-- 
Jeff Garzik      | The difference between America and England is that
Building 1024    | the English think 100 miles is a long distance and
MandrakeSoft     | the Americans think 100 years is a long time.
                 |      (random fortune)

      reply	other threads:[~2001-04-23 20:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-23 20:15 [PATCH] some network __init code Andrzej Krzysztofowicz
2001-04-23 20:23 ` Jeff Garzik [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=3AE48F57.2A859328@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ankry@green.mif.pg.gda.pl \
    --cc=linux-kernel@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