From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Adrian Bunk <bunk@kernel.org>
Cc: Mike Galbraith <efault@gmx.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] let GROUP_SCHED depend on BROKEN
Date: Tue, 27 May 2008 11:28:12 +0100 [thread overview]
Message-ID: <20080527112812.63697b39@core> (raw)
In-Reply-To: <20080527102654.GB20938@cs181133002.pp.htv.fi>
> - as long as we allow hardware drivers to depend on EXPERIMENTAL we
> force many users to enable EXPERIMENTAL
> - the EXPERIMENTAL dependencies in many areas of the kernel are so
> out of sync with the actual code quality that the presence or absence
> of such a dependency isn't a clear indication of the current status
It would probably be very useful to actually do an assessment of what is
marked experimental especially a cross compare with enterprise distros as
what they ship they have reviewed and consider supportable.
Alan
next prev parent reply other threads:[~2008-05-27 10:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 8:58 [RFC: 2.6 patch] let GROUP_SCHED depend on BROKEN Adrian Bunk
2008-05-27 9:47 ` Mike Galbraith
2008-05-27 10:04 ` Mike Galbraith
2008-05-27 10:26 ` Adrian Bunk
2008-05-27 10:28 ` Alan Cox [this message]
2008-05-27 11:27 ` Mike Galbraith
2008-05-27 11:47 ` Peter Zijlstra
2008-05-27 13:08 ` Adrian Bunk
2008-05-27 14:17 ` Peter Zijlstra
2008-05-27 17:30 ` Thomas Gleixner
2008-05-27 19:18 ` Adrian Bunk
2008-05-27 14:22 ` Ingo Molnar
2008-05-27 17:53 ` Adrian Bunk
2008-05-27 18:17 ` Mike Galbraith
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=20080527112812.63697b39@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.