public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: christophe barbe <christophe.barbe.ml@online.fr>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] export pci_table in aic7xxx for Hotplug
Date: Tue, 16 Oct 2001 14:41:34 +1000	[thread overview]
Message-ID: <20015.1003207294@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 15 Oct 2001 14:31:47 CST." <200110152031.f9FKVlY56104@aslan.scsiguy.com>

On Mon, 15 Oct 2001 14:31:47 -0600, 
"Justin T. Gibbs" <gibbs@scsiguy.com> wrote:
>>I have defined __NO_VERSION__ before including module.h because in my
>>understanding this is required when you include it in a multi-files module.
>>Only one file must include module.h without defining the __NO_VERSION__.
>
>I can find no reference to "__NO_VERSION__" in module.h or the files
>it includes.   Perhaps this is a requirement for old kernels?

__NO_VERSION__ used to be required in multi part modules but too many
people got it wrong so I removed it in 2.3 kernels, fixing the problem
in a diffrent way.  Removing all defines of __NO_VERSION__ is on my
clean up list for 2.5.


  parent reply	other threads:[~2001-10-16  4:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-15 17:59 [PATCH] export pci_table in aic7xxx for Hotplug christophe barbe
2001-10-15 19:02 ` Justin T. Gibbs
2001-10-15 20:23   ` christophe barbe
2001-10-15 20:31     ` Justin T. Gibbs
2001-10-15 20:45       ` christophe barbe
2001-10-16  4:41       ` Keith Owens [this message]
2001-10-16 16:17       ` christophe barbe
2001-10-16 20:16         ` christophe barbé
2001-10-16 20:50           ` christophe barbé
2001-10-16 20:59             ` christophe barbe
2001-10-16 21:18             ` Justin T. Gibbs

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=20015.1003207294@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=christophe.barbe.ml@online.fr \
    --cc=gibbs@scsiguy.com \
    --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