From: Simon Horman <horms@verge.net.au>
To: kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Michael Neuling <mikey@neuling.org>
Subject: [rfc] Merge kexec-tools into the kernel tree
Date: Wed, 4 Aug 2010 16:06:48 +0900 [thread overview]
Message-ID: <20100804070647.GB24064@verge.net.au> (raw)
Hi,
After all the excitement of relocating kexec-tools from
one location on kernel.org to another last week it was
suggested to me by Michael Neuling that the merging
kexec-tools into the kernel tree would be a good idea.
Given that there have been a bunch of issues with kexec
on power that this would resolve. and there is precedence
for tools in the kernel tree, this sounds entirely reasonable to me.
So with my kexec-tools maintainer hat on, I would like to start
a conversation about this.
In order to move the conversation along I have prepared a tree -
a recent clone of Linus's tree + kexec tools.
http://git.kernel.org/?p=linux/kernel/git/horms/kexec-tools-in-kernel-tree.git
I think that a good next step would be to get this tree into linux-next.
And then if all goes well, as Linus to pull the change some time in the future.
For reference the steps taken to make the tree above were roughly as follows.
Thanks to Michael for assistance with this.
git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
git clone git://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git
cd linux-2.6
git remote add -f kexec ../kexec-tools
git merge -s ours --no-commit kexec/master
git read-tree --prefix=tools/kexec/ -u kexec/master
git commit -m "Merge kexec-tools into subdirectory tools/kexec"
next reply other threads:[~2010-08-04 7:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 7:06 Simon Horman [this message]
2010-08-04 7:22 ` Américo Wang
2010-08-04 7:34 ` Eric W. Biederman
2010-08-04 15:05 ` Andi Kleen
2010-08-04 23:11 ` Michael Neuling
2010-08-05 0:04 ` Eric W. Biederman
2010-08-05 1:19 ` Michael Neuling
2010-08-05 3:26 ` Américo Wang
2010-08-05 3:22 ` Américo Wang
2010-08-04 8:08 ` Bernhard Walle
2010-08-04 12:26 ` Neil Horman
2010-08-05 6:40 ` Simon Horman
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=20100804070647.GB24064@verge.net.au \
--to=horms@verge.net.au \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikey@neuling.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
all inboxes | Powered by JetHome®