public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Ingo Molnar <mingo@elte.hu>
Cc: Pekka Enberg <penberg@kernel.org>,
	Sasha Levin <levinsasha928@gmail.com>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] config: Add 'make kvmconfig'
Date: Thu, 27 Oct 2011 14:51:52 +0200	[thread overview]
Message-ID: <4EA953E8.4020004@suse.cz> (raw)
In-Reply-To: <20111027123713.GB22032@elte.hu>

On 27.10.2011 14:37, Ingo Molnar wrote:
> 
> * Pekka Enberg <penberg@kernel.org> wrote:
> 
>> On Thu, Oct 27, 2011 at 3:07 PM, Sasha Levin <levinsasha928@gmail.com> wrote:
>>> This patch adds 'make kvmconfig' which allows to add KVM guest support
>>> to a config file.
>>>
>>> This allows for easier testing of configurations under virtualized
>>> environments.
>>>
>>> Cc: Ingo Molnar <mingo@elte.hu>
>>> Cc: Linus Torvalds <torvalds@linux-foundation.org>
>>> Cc: Michal Marek <mmarek@suse.cz>
>>> Cc: Pekka Enberg <penberg@cs.helsinki.fi>
>>> Cc: linux-kbuild@vger.kernel.org
>>> Cc: linux-kernel@vger.kernel.org
>>> Suggested-by: Ingo Molnar <mingo@elte.hu>
>>> Signed-off-by: Sasha Levin <levinsasha928@gmail.com>
>>
>> Acked-by: Pekka Enberg <penberg@kernel.org>
>>
>> Btw, Michal, if people are OK with the patch I'd really love to 
>> take this patch in my kvmtool git tree to have it contained in a 
>> single pull request.
> 
> I like the feature - i hope it's expressed in the right Kbuild-ish 
> fashion.
> 
> Acked-by: Ingo Molnar <mingo@elte.hu>

I hope we won't now also be getting make nfsconfig, make paeconfig and
whatnot :). Also, the lists of select statements might need updates from
time to time, if new dependencies appear.

Michal

  reply	other threads:[~2011-10-27 12:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 12:07 [PATCH] config: Add 'make kvmconfig' Sasha Levin
2011-10-27 12:12 ` Pekka Enberg
2011-10-27 12:37   ` Ingo Molnar
2011-10-27 12:51     ` Michal Marek [this message]
2011-10-27 13:34       ` Ingo Molnar
2011-10-27 14:11       ` Pekka Enberg
2011-10-27 14:32         ` Michal Marek
2011-10-27 15:05           ` Arnaud Lacombe
2011-10-27 15:19         ` Arnaud Lacombe
2011-10-27 15:30           ` Pekka Enberg
2011-10-27 18:05 ` Rabin Vincent
2011-10-27 20:46   ` Sasha Levin
2011-10-27 19:34 ` Sam Ravnborg
2011-10-28  7:03   ` Ingo Molnar
2011-10-28  7:23     ` Sasha Levin
2011-10-28  7:39       ` Ingo Molnar
2011-10-28  7:47         ` Sasha Levin
2011-10-28  7:52           ` Ingo Molnar
2011-10-28  7:52     ` Geert Uytterhoeven
2011-10-28  7:54       ` Ingo Molnar
2011-10-28 12:08         ` Matthias Schniedermeyer
2011-10-28 12:29           ` Ingo Molnar
2011-10-28 13:05             ` Matthias Schniedermeyer
2011-11-02  8:41               ` Ingo Molnar
2011-11-02  9:07                 ` Michal Marek
2011-11-02  9:17                   ` Ingo Molnar
2011-11-02  9:24                     ` Michal Marek
2011-11-02  9:39                       ` Ingo Molnar
2011-11-02 10:06                         ` Pekka Enberg
2011-10-28  9:16       ` Sasha Levin

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=4EA953E8.4020004@suse.cz \
    --to=mmarek@suse.cz \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@kernel.org \
    --cc=torvalds@linux-foundation.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