From: Bernhard Walle <bernhard@bwalle.de>
To: Simon Horman <horms@verge.net.au>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Michael Neuling <mikey@neuling.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [rfc] Merge kexec-tools into the kernel tree
Date: Wed, 4 Aug 2010 10:08:13 +0200 [thread overview]
Message-ID: <20100804080813.GA20178@bwalle.de> (raw)
In-Reply-To: <20100804070647.GB24064@verge.net.au>
* Simon Horman <horms@verge.net.au> [2010-08-04 09:06]:
>
> 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.
Well, honestly I don't understand the reason behind it.
If it's about dependencies between the kexec binary and the kernel
version -- there are also dependencies between makedumpfile and crash to
the kernel version. Should we move makedumpfile and crash in the kernel
tree, too (which means that we have a GDB copy in the kernel tree)?
Regards,
Bernhard
next prev parent reply other threads:[~2010-08-04 8:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 7:06 [rfc] Merge kexec-tools into the kernel tree Simon Horman
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 [this message]
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=20100804080813.GA20178@bwalle.de \
--to=bernhard@bwalle.de \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--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