public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Stephen Boyd <bebarino@gmail.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	Nir Tzachar <nir.tzachar@gmail.com>
Subject: Re: [PATCH] nconfig: Fix segfault when help contains special characters
Date: Fri, 23 Jul 2010 11:25:50 +0200	[thread overview]
Message-ID: <4C49601E.5060605@suse.cz> (raw)
In-Reply-To: <1279868654-15743-1-git-send-email-bebarino@gmail.com>

On 23.7.2010 09:04, Stephen Boyd wrote:
> nconfig segfaults when help text contains the character '%'. For a quick
> example, navigate to the kernel compression options and get the help for
> bzip2. Doing so triggers a call to mvwprintw() with a string containing
> '%' and no extra arguments to fill in the specifier's value. Fix this
> case by printing the literal string retrieved from the kconfig.

Thanks, applied.

Michal

  reply	other threads:[~2010-07-23  9:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-23  7:04 [PATCH] nconfig: Fix segfault when help contains special characters Stephen Boyd
2010-07-23  9:25 ` Michal Marek [this message]
2010-07-25  8:30   ` Nir Tzachar

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=4C49601E.5060605@suse.cz \
    --to=mmarek@suse.cz \
    --cc=bebarino@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nir.tzachar@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