From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: modversions.h source pollution in 2.4
Date: Sun, 04 Feb 2001 19:12:02 -0500 [thread overview]
Message-ID: <3A7DEFD2.F5BF5175@mandrakesoft.com> (raw)
In-Reply-To: <26206.981331639@kao2.melbourne.sgi.com>
Keith Owens wrote:
> Maintainers: please fix these sources by removing modversions.h.
[...]
> drivers/net/epic100.c
> drivers/net/starfire.c
Fixed.
Jeff
--
Jeff Garzik | "You see, in this world there's two kinds of
Building 1024 | people, my friend: Those with loaded guns
MandrakeSoft | and those who dig. You dig." --Blondie
-
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/
next prev parent reply other threads:[~2001-02-05 0:12 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 [this message]
2001-02-05 18:16 ` Andreas Dilger
2001-02-05 18:21 ` Alan Cox
2001-02-05 20:23 ` Keith Owens
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=3A7DEFD2.F5BF5175@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=kaos@ocs.com.au \
--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