From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Ingo Molnar <mingo@elte.hu>,
Rene Herman <rene.herman@keyaccess.nl>,
Andrew Morton <akpm@osdl.org>, Yinghai Lu <yhlu.kernel@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: kill arch/x86/kernel/mpparse.c debugging printk.
Date: Mon, 11 Aug 2008 22:46:54 +0400 [thread overview]
Message-ID: <20080811184654.GC18969@lenovo> (raw)
In-Reply-To: <20080811184257.GB18969@lenovo>
[Cyrill Gorcunov - Mon, Aug 11, 2008 at 10:42:57PM +0400]
...
| |
| | - in this case your first change was the obvious one and your NULL fix
| | and your cleanup to the parameter expose a fundamental weakness of
| | early_param conversions - and i think highlighting that as separate
| | commits might give someone ideas to improve the early_param()
| | facility, if they see the fix patterns.
|
| Ingo - I think the problem with early_param is not NULL itself but
| rather - what is the right way to deal with boot params? I mean we
| could pass empty string (not NULL) in case of argument absence _but_ would it
| be the right way? If you remember when I sent first series for early_param
| checking (and actually there are number of same issue exists for example
| in s390 arch) - I was asking community what is the best way - since I'm not
| that strong in interface engineering - i prefer fix the bugs :)
|
| |
| | - Also, the NULL condition is obscure, so there's no bisection breakage
| | risk and it's the easiest for me to do append-only patches. The effort
| | and thought process you and Cyrill have put into it deserve a separate
| | commit as well anyway - and others might learn from it when looking at
| | logs.
| |
| | Ingo
| |
| - Cyrill -
here is the link to that message
http://lkml.org/lkml/2008/7/9/222
- Cyrill -
next prev parent reply other threads:[~2008-08-11 18:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 16:43 [PATCH] x86: kill arch/x86/kernel/mpparse.c debugging printk Rene Herman
2008-08-11 12:20 ` Ingo Molnar
2008-08-11 15:44 ` Rene Herman
2008-08-11 15:45 ` Rene Herman
2008-08-11 16:45 ` Cyrill Gorcunov
2008-08-11 17:20 ` Rene Herman
2008-08-11 17:41 ` Ingo Molnar
2008-08-11 18:06 ` Rene Herman
2008-08-11 18:33 ` Ingo Molnar
2008-08-11 18:42 ` Cyrill Gorcunov
2008-08-11 18:46 ` Cyrill Gorcunov [this message]
2008-08-11 18:49 ` Ingo Molnar
2008-08-11 19:01 ` Cyrill Gorcunov
2008-08-11 18:54 ` Rene Herman
2008-08-11 16:38 ` Ingo Molnar
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=20080811184654.GC18969@lenovo \
--to=gorcunov@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rene.herman@keyaccess.nl \
--cc=yhlu.kernel@gmail.com \
/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