From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: thgodef@nerim.net
Subject: Re: BUG in Linux 2.6.16/2.6.16.1 (compilation failure of third party software)
Date: Tue, 28 Mar 2006 17:03:37 -0600 [thread overview]
Message-ID: <4429C0C9.7050303@shaw.ca> (raw)
In-Reply-To: <5Vr7d-4VR-15@gated-at.bofh.it>
Thierry Godefroy wrote:
> Paragon_NTFS_3.x.v5.1 fails to compile (with gcc v3.4.3) with the following
> errors:
I don't think compilation failures of out-of-tree drivers is considered
a bug. It's the responsibility of those drivers to keep up to date with
kernel changes.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-03-28 23:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5Vr7d-4VR-15@gated-at.bofh.it>
2006-03-28 23:03 ` Robert Hancock [this message]
[not found] ` <5Vvkv-2MB-27@gated-at.bofh.it>
[not found] ` <5VvNw-3B1-3@gated-at.bofh.it>
2006-03-29 2:20 ` BUG in Linux 2.6.16/2.6.16.1 (compilation failure of third party software) Robert Hancock
2006-03-28 18:29 Thierry Godefroy
2006-03-28 22:51 ` Lee Revell
2006-03-28 23:21 ` Thierry Godefroy
2006-03-29 4:42 ` Arjan van de Ven
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=4429C0C9.7050303@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=thgodef@nerim.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