From: Keith Owens <kaos@ocs.com.au>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: modversions.h source pollution in 2.4
Date: Tue, 06 Feb 2001 07:23:25 +1100 [thread overview]
Message-ID: <2287.981404605@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Mon, 05 Feb 2001 11:16:50 PDT." <200102051816.f15IGoT11015@webber.adilger.net>
On Mon, 5 Feb 2001 11:16:50 -0700 (MST),
Andreas Dilger <adilger@turbolinux.com> wrote:
>Keith Owens writes:
>> Maintainers: please fix these sources by removing modversions.h.
>
>It is not clear from your posting if anything other than removing the
>"#include <linux/modversions.h>" line is needed... Also, what kernel
>versions is this needed for? The LVM code uses a common source file
>for 2.2 and 2.4, so should the #include stay in for 2.2?
It should be as simple as removing #include <linux/modversions.h>, and
it applies to all kernels, back to 2.1.81.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-05 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 0:07 modversions.h source pollution in 2.4 Keith Owens
2001-02-05 0:12 ` Jeff Garzik
2001-02-05 18:16 ` Andreas Dilger
2001-02-05 18:21 ` Alan Cox
2001-02-05 20:23 ` Keith Owens [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=2287.981404605@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=adilger@turbolinux.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 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.