From: "David S. Miller" <davem@redhat.com>
To: rusty@rustcorp.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] module_name()
Date: Tue, 12 Nov 2002 14:03:57 -0800 (PST) [thread overview]
Message-ID: <20021112.140357.81690208.davem@redhat.com> (raw)
In-Reply-To: <20021112174741.6073E2C2B2@lists.samba.org>
From: Rusty Russell <rusty@rustcorp.com.au>
Date: Wed, 13 Nov 2002 04:32:58 +1100
I prefer this: it also has the advantage of ensuring the name of
built-in modules is consistent across the kernel.
I'd rather get NULL for built-in, this also eliminates
the issue of having umpteen "[built-in]" string copies in
the kernel since this is expanded by an inline.
next prev parent reply other threads:[~2002-11-12 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 17:32 [PATCH] module_name() Rusty Russell
2002-11-12 20:39 ` Robert Love
2002-11-12 22:00 ` David S. Miller
2002-11-12 22:03 ` David S. Miller [this message]
2002-11-13 10:04 ` Rusty Russell
2002-11-13 10:56 ` David S. Miller
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=20021112.140357.81690208.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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