From: arjan@fenrus.demon.nl
To: linux@mswinxp.net (Lee Packham)
Cc: linux-kernel@vger.kernel.org
Subject: Re: kbuild 2.5 preventing mixture of compilers
Date: Thu, 01 Nov 2001 08:37:35 +0000 [thread overview]
Message-ID: <E15zDLz-0008Tf-00@fenrus.demon.nl> (raw)
In-Reply-To: <2644.192.168.2.1.1004602385.squirrel@mail.mswinxp.net>
In article <2644.192.168.2.1.1004602385.squirrel@mail.mswinxp.net> you wrote:
> IMHO, that is a good idea... almost.
> What about companies that maintain closed source driver modules for their
> hardware?
> I know a lot of people here will say, 'well they should open source them
> then'. However, some companies don't want to for their own reasons and
> this 'could' blow them out the water a bit and affect end users.
If a different compiler version is known to break (and Keith says he has
seen that in practice, and I can see it happen as well given that a few
kernel headers depend on compiler version), the vendor in question is better
off being informed about the incompatibility. He _already_ has to have an
exact match on the kernel version and the other symbols, so adding the
compiler to that is not an extra burden, just a "oh we goofed" prevention..
prev parent reply other threads:[~2001-11-01 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-01 0:43 Keith Owens
2001-11-01 8:13 ` Lee Packham
2001-11-01 8:37 ` arjan [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=E15zDLz-0008Tf-00@fenrus.demon.nl \
--to=arjan@fenrus.demon.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@mswinxp.net \
/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
all inboxes | Powered by JetHome®