From: Rusty Russell <rusty@rustcorp.com.au>
To: pradeep singh <pradeep.rautela@gmail.com>
Cc: virtualization-list <virtualization@lists.linux-foundation.org>
Subject: Re: [Q]lguest git repo location?
Date: Mon, 06 Aug 2007 10:46:48 +1000 [thread overview]
Message-ID: <1186361208.32112.29.camel@localhost.localdomain> (raw)
In-Reply-To: <a901b49a0708040714n52d83eb4ub39d5b76acb1032b@mail.gmail.com>
On Sat, 2007-08-04 at 19:44 +0530, pradeep singh wrote:
> HI Rusty,
>
> I wanted to play with lguest. As it was recently merge upstream by
> Linus, i took a look and the location looks like driver/lguest*.
>
> Unfortunately my local git repo cannot get the 2.6.23-rc2 changes from
> upstream somehow :-/.[duh... says "Cannot get the repository state
> from http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git"].
> i do not know what i am doing wrong.
>
> Coming back to point -
> Do you maintain a lguest git repository somewhere? So that i can clone
> it and experiment with it?
Hi Pradeep!
I don't keep a git repository; I keep some patches which fits my
working style better. However, the 2.6.23-rc2 tree should work with
this one patch:
==
Lguest drivers need to default to "Y" otherwise they're never selected
for new builds. We don't bother prompting, because they're less than
4k combined.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
---
drivers/lguest/Kconfig | 2 ++
1 file changed, 2 insertions(+)
===================================================================
--- a/drivers/lguest/Kconfig
+++ b/drivers/lguest/Kconfig
@@ -21,8 +21,10 @@ config LGUEST_GUEST
config LGUEST_NET
tristate
+ default y
depends on LGUEST_GUEST && NET
config LGUEST_BLOCK
tristate
+ default y
depends on LGUEST_GUEST && BLOCK
next prev parent reply other threads:[~2007-08-06 0:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 14:14 [Q]lguest git repo location? pradeep singh
2007-08-04 15:14 ` pradeep singh
2007-08-06 0:46 ` Rusty Russell [this message]
2007-08-06 6:57 ` pradeep singh
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=1186361208.32112.29.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=pradeep.rautela@gmail.com \
--cc=virtualization@lists.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;
as well as URLs for NNTP newsgroup(s).