From: David Woodhouse <dwmw2@infradead.org>
To: Satyam Sharma <satyam@infradead.org>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mtd@lists.infradead.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [2/2] 2.6.23-rc5: known regressions with patches
Date: Thu, 06 Sep 2007 11:28:11 +0100 [thread overview]
Message-ID: <1189074491.2745.78.camel@shinybook.infradead.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0709061600250.3781@enigma.security.iitk.ac.in>
On Thu, 2007-09-06 at 16:04 +0530, Satyam Sharma wrote:
> You shouldn't push this even for 2.6.24 ... I can't see why/how a runtime
> BUG() scores over erroring out at build-time itself. And if there is no
> codepath that leads to that BUG() at runtime, then what's the point of
> adding dead code ...
>
> So I wonder if what you're actually looking for is some kind of Kconfig
> dependencies that will *prevent* the kind of .config from being generated
> that Ingo ran into ?
I looked at that but decided against it. There's too much hand-holding
and arbitrary 'automatic' crap in the Kconfig crap already, and I
couldn't see a way to do it that didn't make that worse.
As long as we no longer break randconfig builds, it'll be fine. It's not
as if people _run_ those kernels, let alone actually exercise the code
path in question.
--
dwmw2
next prev parent reply other threads:[~2007-09-06 10:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46DBDCF4.6040805@googlemail.com>
2007-09-03 10:11 ` [2/2] 2.6.23-rc5: known regressions with patches Michal Piotrowski
2007-09-06 9:59 ` David Woodhouse
2007-09-06 10:34 ` Satyam Sharma
2007-09-06 10:28 ` David Woodhouse [this message]
2007-09-07 23:39 ` Michal Piotrowski
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=1189074491.2745.78.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mingo@elte.hu \
--cc=satyam@infradead.org \
--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