linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: inconvenience when hand editing DEBUG_LL in .config
Date: Sat, 21 Jan 2012 00:34:07 +0100	[thread overview]
Message-ID: <20120120233407.GQ4066@pengutronix.de> (raw)
In-Reply-To: <20120120192750.GE11845@n2100.arm.linux.org.uk>

On Fri, Jan 20, 2012 at 07:27:50PM +0000, Russell King - ARM Linux wrote:
> On Fri, Jan 20, 2012 at 05:40:36PM +0100, Uwe Kleine-K?nig wrote:
> > Hello,
> > 
> > usually when I want to change a single kernel option I just open .config
> > in my editor, remove the line for the config item I want to change and
> > run oldconfig. For DEBUG_LL (defined in arch/arm/Kconfig.debug) this
> > doesn't work as usual though.
> > 
> > On 3.3-rc1 the following happens:
> > 
> > 	make ARCH=arm at91rm9200_defconfig
> > 	sed -i /CONFIG_DEBUG_LL/d .config
> 
> Note that this deletes two entries.  Use /CONFIG_DEBUG_LL\\\>/d to delete
> just one (or get rid of two of those \ and use ' to quote it.)
After at91rm9200_defconfig CONFIG_DEBUG_LL is not set, so
CONFIG_DEBUG_LL_UART_NONE and the other options from that choice don't
appear in .config and so for me only a single line is removed. But
that's only an uninteresting detail.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2012-01-20 23:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-20 16:40 inconvenience when hand editing DEBUG_LL in .config Uwe Kleine-König
2012-01-20 19:27 ` Russell King - ARM Linux
2012-01-20 23:34   ` Uwe Kleine-König [this message]
2012-01-20 20:31 ` Arnaud Lacombe

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=20120120233407.GQ4066@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).