From: Ingo Molnar <mingo@elte.hu>
To: Jan Beulich <JBeulich@novell.com>
Cc: David Rientjes <rientjes@google.com>, Tejun Heo <tj@kernel.org>,
tglx@linutronix.de, linux-kernel@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86: unify "numa=" command line option handling
Date: Fri, 7 Jan 2011 16:12:54 +0100 [thread overview]
Message-ID: <20110107151254.GA418@elte.hu> (raw)
In-Reply-To: <4D2730BE020000780002B040@vpn.id2.novell.com>
* Jan Beulich <JBeulich@novell.com> wrote:
> >>> On 07.01.11 at 15:22, Ingo Molnar <mingo@elte.hu> wrote:
> > Your -stable comment above made it appear to me as if you knew about a
> > specific
> > system that crashed this way? As long as it's only theoretical i'm not sure
> > it
> > warrants a -stable backport.
>
> Yes, I do have a system affected (which made me craft the patch
> in the first place).
In that case it's very useful to start the commit with:
System XYZ crashes during bootup due to a bug in numa= command line option
handling.
That will also cause me to add an immediate -stable backport tag from me, even if
you dont add it. Keeping it all optional and theoretical with 'it may crash' wording
just hides the essential piece of information that there's a real system affected by
the bug.
Thanks,
Ingo
next prev parent reply other threads:[~2011-01-07 15:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 17:02 [PATCH] x86: unify "numa=" command line option handling Jan Beulich
2011-01-06 20:36 ` David Rientjes
2011-01-07 7:51 ` Jan Beulich
2011-01-07 9:58 ` David Rientjes
2011-01-07 10:06 ` Jan Beulich
2011-01-07 12:57 ` Ingo Molnar
2011-01-07 13:32 ` Jan Beulich
2011-01-07 14:22 ` Ingo Molnar
2011-01-07 14:26 ` Jan Beulich
2011-01-07 15:12 ` Ingo Molnar [this message]
2011-01-07 19:55 ` David Rientjes
2011-01-10 8:14 ` Jan Beulich
2011-01-07 20:37 ` Tejun Heo
2011-01-07 20:33 ` Tejun Heo
2011-01-07 20:36 ` David Rientjes
2011-01-07 20:43 ` Tejun Heo
2011-01-07 20:46 ` David Rientjes
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=20110107151254.GA418@elte.hu \
--to=mingo@elte.hu \
--cc=JBeulich@novell.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.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