public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	"valentinrothberg@gmail.com" <valentinrothberg@gmail.com>,
	"rupran@einserver.de" <rupran@einserver.de>,
	"stefan.hengelein@fau.de" <stefan.hengelein@fau.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] mm: MEMTEST depends on MEMBLOCK
Date: Fri, 20 Mar 2015 11:52:06 +0100	[thread overview]
Message-ID: <1426848726.23529.41.camel@x220> (raw)
In-Reply-To: <550BF8E2.9020002@arm.com>

On Fri, 2015-03-20 at 10:39 +0000, Vladimir Murzin wrote:
> I should have tested it before...

Valentin proposed an update to scripts/checkkconfigsymbols.py in 
https://lkml.org/lkml/2015/3/16/190 . It (or something like it) should
have helped testing for typos like that:
    python scripts/checkkconfigsymbols.py --commit b47818820b392273da5470975a29aca4cba92cb4
    MEMBLOCK	lib/Kconfig.debug

Which is actually rather cool!

Valentin, what's the status of that update?


Paul Bolle


  reply	other threads:[~2015-03-20 10:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  9:03 [PATCH -next] mm: MEMTEST depends on MEMBLOCK Guenter Roeck
2015-03-13  9:55 ` Vladimir Murzin
2015-03-16 11:04 ` Geert Uytterhoeven
2015-03-20 10:23 ` Paul Bolle
2015-03-20 10:39   ` Vladimir Murzin
2015-03-20 10:52     ` Paul Bolle [this message]
2015-03-20 10:59       ` Valentin Rothberg
2015-03-20 14:34       ` Stefan Hengelein
2015-03-20 15:11         ` Paul Bolle

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=1426848726.23529.41.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=rupran@einserver.de \
    --cc=stefan.hengelein@fau.de \
    --cc=valentinrothberg@gmail.com \
    --cc=vladimir.murzin@arm.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