From: Valdis.Kletnieks@vt.edu
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Ingo Molnar <mingo@elte.hu>,
"Giacomo A. Catenazzi" <cate@cateee.net>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: using LKML for subsystem development
Date: Sun, 27 Jan 2008 02:37:34 -0500 [thread overview]
Message-ID: <15602.1201419454@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sat, 26 Jan 2008 14:31:01 +0100." <479B3615.9000903@s5r6.in-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
On Sat, 26 Jan 2008 14:31:01 +0100, Stefan Richter said:
> Does your laptop have for example chained sg lists? :-)
Beats me - I don't see it on an 'lspci' ;) But I'm pretty sure it doesn't
have a 'powerpc' in it, so those threads get *totally* skipped...
My point was "personal interest in the domain" may not be a great way to
tell if a given thread has a stability risk - but I suspect that for the vast
majority of testers like myself who aren't paid to be kernel hackers, if it
isn't something they can trip over on the one or two machines they can easily
test on, it isn't code they're going to review....
(Note that it extends past just hardware too - my config has selinux in it,
so those threads at least *might* get looked at. cpusets or ocfs2? If I
read those threads, it's probably by accident... :)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2008-01-27 7:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 23:17 Linux 2.6.24 Linus Torvalds
2008-01-24 23:41 ` Linus Torvalds
2008-01-25 9:10 ` Giacomo A. Catenazzi
2008-01-25 9:58 ` Valdis.Kletnieks
2008-01-25 11:58 ` Rafael J. Wysocki
2008-01-25 12:34 ` Giacomo A. Catenazzi
2008-01-25 23:50 ` Stefan Richter
2008-01-26 0:42 ` using LKML for subsystem development (was Re: Linux 2.6.24) Stefan Richter
2008-01-26 3:28 ` Valdis.Kletnieks
2008-01-26 13:31 ` using LKML for subsystem development Stefan Richter
2008-01-27 7:37 ` Valdis.Kletnieks [this message]
2008-01-26 11:28 ` using LKML for subsystem development (was Re: Linux 2.6.24) Ingo Molnar
2008-01-26 14:07 ` using LKML for subsystem development David Miller
2008-01-26 14:45 ` Stefan Richter
2008-01-26 14:25 ` Stefan Richter
2008-02-01 9:40 ` Ingo Molnar
2008-02-01 19:53 ` Stefan Richter
2008-01-26 3:19 ` Linux 2.6.24 Valdis.Kletnieks
2008-01-25 11:35 ` Ingo Molnar
2008-01-25 10:11 ` [PATCH] linux-2.6.24/drivers/hid/hid-input.c Philipp Matthias Hahn
2008-01-25 10:30 ` Jiri Kosina
2008-02-03 12:35 ` Linux 2.6.24 Jan Engelhardt
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=15602.1201419454@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=cate@cateee.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=stefanr@s5r6.in-berlin.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®