LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Adrian Bunk <bunk@kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Tilman Schmidt <tilman@imap.cc>, Greg KH <gregkh@suse.de>
Subject: Re: 2.6.25-rc2: Reported regressions from 2.6.24
Date: Mon, 18 Feb 2008 14:49:08 +0100 [thread overview]
Message-ID: <20080218134908.GB28851@elte.hu> (raw)
In-Reply-To: <200802181235.31503.rjw@sisk.pl>
* Rafael J. Wysocki <rjw@sisk.pl> wrote:
> Well, my definition of a regression from 2.6.24 is that it happens
> when someone takes a .config that worked with 2.6.24, configures the
> kernel with that, leaving the defaults for the options he is _asked_
> _for_, and the resulting kernel doesn't work as expected.
yep, and that's how users determine whether "the new kernel works", so
it's what we follow as well.
Ingo
next prev parent reply other threads:[~2008-02-18 13:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 22:03 2.6.25-rc2: Reported regressions from 2.6.24 Rafael J. Wysocki
2008-02-17 22:54 ` Jiri Kosina
2008-02-17 23:06 ` Mariusz Kozlowski
2008-02-17 23:06 ` Rafael J. Wysocki
2008-02-17 23:13 ` Adrian Bunk
2008-02-18 3:39 ` Andrey Borzenkov
2008-02-18 5:37 ` Arjan van de Ven
2008-02-18 11:24 ` Rafael J. Wysocki
2008-02-18 16:51 ` Arjan van de Ven
2008-02-18 7:02 ` Carlos Eduardo Medaglia Dyonisio
2008-02-18 11:27 ` Rafael J. Wysocki
2008-02-18 13:01 ` Carlos E. M. Dyonisio
2008-02-18 8:52 ` Jiri Slaby
2008-02-18 9:43 ` Alexey Dobriyan
2008-02-18 9:49 ` Ingo Molnar
2008-02-18 9:59 ` Jiri Slaby
2008-02-18 10:42 ` Alexey Dobriyan
2008-02-18 11:35 ` Rafael J. Wysocki
2008-02-18 13:49 ` Ingo Molnar [this message]
2008-02-18 10:17 ` Dhaval Giani
2008-02-18 11:38 ` Rafael J. Wysocki
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=20080218134908.GB28851@elte.hu \
--to=mingo@elte.hu \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@kernel.org \
--cc=gregkh@suse.de \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tilman@imap.cc \
--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;
as well as URLs for NNTP newsgroup(s).