From: Paul Bolle <pebolle@tiscali.nl>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: valentinrothberg@gmail.com, rupran@einserver.de,
stefan.hengelein@fau.de,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"mhocko@suse.cz" <mhocko@suse.cz>
Subject: Re: mmotm 2015-04-01-14-54 uploaded
Date: Thu, 02 Apr 2015 20:52:03 +0200 [thread overview]
Message-ID: <1428000723.10518.70.camel@x220> (raw)
In-Reply-To: <551D0101.6000301@arm.com>
On Thu, 2015-04-02 at 09:42 +0100, Vladimir Murzin wrote:
> It was noticed by Paul Bolle (and his clever bot) that patch above
> simply disables MEMTEST altogether [1].
This needs correcting.
The clever bot is a project of Andreas Ruprecht, Stefan Hengelein, and
Valentin Rothberg. I've only been cheering their efforts.
I noticed this issue because I wrote a 800 line perl monster that checks
this stuff. It's only slightly more advanced than
scripts/checkkconfigsymbols.py (which Stefan and Valentin wrote). And
I'm sure that python script would have spotted this issue too.
Thanks,
Paul Bolle
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2015-04-02 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 21:55 mmotm 2015-04-01-14-54 uploaded akpm
2015-04-02 8:42 ` Vladimir Murzin
2015-04-02 18:52 ` Paul Bolle [this message]
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=1428000723.10518.70.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=rupran@einserver.de \
--cc=sfr@canb.auug.org.au \
--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;
as well as URLs for NNTP newsgroup(s).