Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org,
	Greg KH <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
	Michal Marek <mmarek@suse.cz>
Subject: Re: [PATCH] scripts/config: properly report and set string options
Date: Tue, 10 Apr 2012 20:33:18 -0500	[thread overview]
Message-ID: <20120411013318.GD11506@burratino> (raw)
In-Reply-To: <201204110107.01273.yann.morin.1998@free.fr>

Yann E. MORIN wrote:

> The scenario involves an upper-layer build system that:
>   - is responsible for settings the kernel options based on global
>     configuration (eg. the same kernel build for different boards)
>     and/or options set by users (eg. I want USB camera support)
>   - uses scripts/config to set/unset options rather than implementing
>     its own logic
>   - in this case the version string can be set to include the user's
>     name, which may contain double-quotes (eg. John "Ripper" Smith)

Thanks for explaining.  That makes sense.

I agree that it doesn't sound like enough of a show-stopper to warrant
inclusion in -stable.  This build system UI bug has existed since
v2.6.31-rc1~335^2~1 (kbuild: add generic --set-str option to
scripts/config, 2009-05-25).

  reply	other threads:[~2012-04-11  1:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-09 12:49 [PATCH] scripts/config: properly report and set string options Yann E. MORIN
2012-04-09 13:22 ` Yann E. MORIN
2012-04-09 14:04 ` Andi Kleen
2012-04-09 15:30 ` Greg KH
2012-04-09 16:02   ` Yann E. MORIN
2012-04-10  8:57     ` Michal Marek
2012-04-10 13:57     ` Jonathan Nieder
2012-04-10 23:07       ` Yann E. MORIN
2012-04-11  1:33         ` Jonathan Nieder [this message]
2012-04-19 21:07 ` Yann E. MORIN
2012-05-15 22:14   ` Michal Marek
2012-05-09 21:27 ` Yann E. MORIN

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=20120411013318.GD11506@burratino \
    --to=jrnieder@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=stable@vger.kernel.org \
    --cc=yann.morin.1998@free.fr \
    /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