From: Pavel Machek <pavel@ucw.cz>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Byungchul Park <byungchul.park@lge.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Randy Dunlap <rdunlap@infradead.org>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Make "Memory Debugging" a menuconfig to ease disabling it all
Date: Fri, 15 Dec 2017 21:21:25 +0100 [thread overview]
Message-ID: <20171215202125.GA14453@amd> (raw)
In-Reply-To: <CAEwRq=pBgf5q16NtF6aQnU4yy9Q+iG3Q6Or5Uqz2NsuBap612A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 522 bytes --]
On Wed 2017-12-13 12:04:17, Vincent Legoll wrote:
> Hello,
>
> looks like this one will need another spin, the kbuild test robot
> found some config mix that has unmet dependencies.
>
> Please drop until v3
While you are at it, care to add a help text? It jumped on me doing
make oldconfig, and I was wondering what it is. It is _not_
self-explanatory.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2017-12-15 20:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 11:53 [PATCH] Make "Memory Debugging" a menuconfig to ease disabling it all Vincent Legoll
2017-12-09 12:40 ` Vincent Legoll
2017-12-09 17:04 ` Randy Dunlap
2017-12-09 17:40 ` [PATCH,v2] " Vincent Legoll
2017-12-09 17:40 ` [PATCH] " Vincent Legoll
2017-12-13 11:04 ` Vincent Legoll
2017-12-15 20:21 ` Pavel Machek [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=20171215202125.GA14453@amd \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=byungchul.park@lge.com \
--cc=geert@linux-m68k.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mingo@kernel.org \
--cc=npiggin@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=vincent.legoll@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