From: Valdis.Kletnieks@vt.edu
To: Christoph Hellwig <hch@infradead.org>
Cc: Nigel Cunningham <nigel@nigel.suspend2.net>,
Arjan van de Ven <arjan@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: VMware, x86_64 and 2.6.21.
Date: Sun, 06 May 2007 03:16:13 -0400 [thread overview]
Message-ID: <18248.1178435773@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sat, 05 May 2007 10:56:09 BST." <20070505095609.GB9935@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
On Sat, 05 May 2007 10:56:09 BST, Christoph Hellwig said:
> On Wed, May 02, 2007 at 01:14:16AM +1000, Nigel Cunningham wrote:
> > > if you want to ask questions about proprietary kernel stuff you're
> > > better off asking the vendor directly, not lkml
> >
> > I did, but given that it the failure only appeared with a change of
> > vanilla kernel version, I didn't think it was out of place to ask here
> > too.
>
> No, it's still totally offtopic here.
I'm not convinced it's *totally* off-topic. I'll agree that third-party
binaries are on their own as far as active support goes, but I don't see
that it's off-topic to post a simple statement-of-fact like "2.6.mumble-rc1
breaks <popular-driver-FOO>" just so it's a *known* issue and people who
search the list archives don't spend forever re-inventing the wheel. Also,
it's quite *possible* that the binary module has tripped over a geniune
regression or bug in the kernel.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-05-06 7:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 5:42 Nigel Cunningham
2007-05-01 6:13 ` Jeff Chua
2007-05-01 6:33 ` Nigel Cunningham
2007-05-01 11:09 ` Jan Engelhardt
2007-05-01 12:51 ` Jeff Chua
2007-05-01 7:24 ` Michael Gerdau
2007-05-01 7:36 ` Nigel Cunningham
2007-05-01 11:10 ` Jan Engelhardt
2007-05-01 11:54 ` Nigel Cunningham
2007-05-01 13:46 ` Mark Lord
2007-05-01 15:09 ` Nigel Cunningham
2007-05-01 14:57 ` Arjan van de Ven
2007-05-01 15:14 ` Nigel Cunningham
2007-05-02 9:30 ` Petr Vandrovec
2007-05-04 11:40 ` Eric W. Biederman
2007-05-04 15:08 ` Zachary Amsden
2007-05-04 20:14 ` Eric W. Biederman
2007-05-04 21:04 ` Zachary Amsden
2007-05-05 9:56 ` Christoph Hellwig
2007-05-05 18:06 ` John Anthony Kazos Jr.
2007-05-06 7:16 ` Valdis.Kletnieks [this message]
2007-05-06 11:08 ` Christoph Hellwig
2007-05-01 6:50 Marcos Pinto
2007-05-01 7:06 ` Nigel Cunningham
2007-05-01 22:38 ` Zachary Amsden
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=18248.1178435773@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=arjan@infradead.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nigel.suspend2.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®