From: Jeff Garzik <jeff@garzik.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, lguest <lguest@ozlabs.org>,
virtualization@lists.linux-foundation.org,
Jeremy Fitzhardinge <jeremy@goop.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [git pull] lguest: paravirt boot code
Date: Tue, 23 Oct 2007 16:37:08 -0400 [thread overview]
Message-ID: <471E5B74.8030900@garzik.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0710230903330.30120@woody.linux-foundation.org>
Linus Torvalds wrote:
>
> On Tue, 23 Oct 2007, Rusty Russell wrote:
>> Well, with that out the way, and some scatterlist fixups, please pull from
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-lguest.git
Also, please add a "lguest: " prefix to all future commits.
Otherwise, in the one-line summary, it is impossible to tell what
portion of the kernel is being updated:
Use "struct boot_params" in example launcher
Loading bzImage directly.
Rename "cr3" to "gpgdir" to avoid x86-specific naming.
Pagetables to use normal kernel types
Move register setup into i386_core.c
Accept elf files that are valid but have sections that can not
be mmap'ed for some reason.
git tools are all keyed to use that first line as a summary of the
changeset, without giving any other context whatsoever. See Linus's
2.6.X-rcY announcements, for example.
This is also described in akpm's
http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt or my
http://linux.yyz.us/patch-format.html
Jeff
next prev parent reply other threads:[~2007-10-23 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 2:37 [git pull] lguest: paravirt boot code Rusty Russell
2007-10-23 2:28 ` Linus Torvalds
2007-10-23 6:03 ` Rusty Russell
2007-10-23 6:55 ` Christian Borntraeger
2007-10-23 7:44 ` Rusty Russell
2007-10-23 16:10 ` Linus Torvalds
2007-10-23 20:37 ` Jeff Garzik [this message]
2007-10-25 5:19 ` Rusty Russell
2007-10-25 6:31 ` Stephen Rothwell
2007-10-25 22:41 ` Linus Torvalds
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=471E5B74.8030900@garzik.org \
--to=jeff@garzik.org \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=lguest@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.org \
--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