From: Ingo Molnar <mingo@kernel.org>
To: Chen Gang <gang.chen@asianux.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH, re-send] Always trap on BUG()
Date: Fri, 26 Jul 2013 00:05:02 +0200 [thread overview]
Message-ID: <20130725220502.GI18254@gmail.com> (raw)
In-Reply-To: <51EF1936.7090801@asianux.com>
* Chen Gang <gang.chen@asianux.com> wrote:
> On 07/23/2013 05:36 PM, Ingo Molnar wrote:
> >
> > (the crazies can keep a separate patch to remove even more of BUG() to win
> > a K or two.)
> >
>
> Excuse me, my English is not quite well, I do not quite understand your
> meaning, could you please repeat again in details or say more clearly ?
I meant: those people who'd like to have the tiny
additional space savings offered by !CONFIG_BUG (and are
crazy enough to live with non-determinism in exchange for a
measly payment of 1 KB), can apply a separate, out of tree
patch just fine and don't need upstream kernel support.
Thanks,
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: mingo@kernel.org (Ingo Molnar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH, re-send] Always trap on BUG()
Date: Fri, 26 Jul 2013 00:05:02 +0200 [thread overview]
Message-ID: <20130725220502.GI18254@gmail.com> (raw)
In-Reply-To: <51EF1936.7090801@asianux.com>
* Chen Gang <gang.chen@asianux.com> wrote:
> On 07/23/2013 05:36 PM, Ingo Molnar wrote:
> >
> > (the crazies can keep a separate patch to remove even more of BUG() to win
> > a K or two.)
> >
>
> Excuse me, my English is not quite well, I do not quite understand your
> meaning, could you please repeat again in details or say more clearly ?
I meant: those people who'd like to have the tiny
additional space savings offered by !CONFIG_BUG (and are
crazy enough to live with non-determinism in exchange for a
measly payment of 1 KB), can apply a separate, out of tree
patch just fine and don't need upstream kernel support.
Thanks,
Ingo
next prev parent reply other threads:[~2013-07-25 22:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 15:38 [PATCH, re-send] Always trap on BUG() Arnd Bergmann
2013-07-05 15:38 ` Arnd Bergmann
2013-07-12 10:15 ` Ingo Molnar
2013-07-12 10:15 ` Ingo Molnar
2013-07-15 22:16 ` Andrew Morton
2013-07-15 22:16 ` Andrew Morton
2013-07-15 22:27 ` Russell King - ARM Linux
2013-07-15 22:27 ` Russell King - ARM Linux
2013-07-15 22:35 ` H. Peter Anvin
2013-07-15 22:35 ` H. Peter Anvin
2013-07-15 22:35 ` H. Peter Anvin
2013-07-15 22:47 ` Russell King - ARM Linux
2013-07-15 22:47 ` Russell King - ARM Linux
2013-07-23 9:36 ` Ingo Molnar
2013-07-23 9:36 ` Ingo Molnar
2013-07-23 9:54 ` H. Peter Anvin
2013-07-23 9:54 ` H. Peter Anvin
2013-07-23 9:54 ` H. Peter Anvin
2013-07-24 0:00 ` Chen Gang
2013-07-24 0:00 ` Chen Gang
2013-07-25 22:05 ` Ingo Molnar [this message]
2013-07-25 22:05 ` Ingo Molnar
2013-07-26 1:05 ` Chen Gang
2013-07-26 1:05 ` Chen Gang
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=20130725220502.GI18254@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=ebiederm@xmission.com \
--cc=gang.chen@asianux.com \
--cc=geert@linux-m68k.org \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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.