mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	"Américo Wang" <xiyou.wangcong@gmail.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	"Andi Kleen" <andi@firstfloor.org>,
	"Michael Neuling" <mikey@neuling.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Neil Horman" <nhorman@redhat.com>
Subject: Re: [rfc] Merge kexec-tools into the kernel tree
Date: Thu, 5 Aug 2010 15:40:12 +0900	[thread overview]
Message-ID: <20100805064011.GB4630@verge.net.au> (raw)
In-Reply-To: <20100804070647.GB24064@verge.net.au>

On Wed, Aug 04, 2010 at 04:06:48PM +0900, Simon Horman wrote:
> 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.

Thanks to everyone for their responses. I think we can safely conclude
that the body of opinion is that its not appropriate for kexec-tools
to be included in the kernel tree. Primarily because it isn't tied
closely to the kernel ABI. As such I withdraw this proposal.

Thanks in particular to those who offered ideas on how to resolve
some of the problems that kexec-tools faces. Lets make those ideas happen.


      parent reply	other threads:[~2010-08-05  6:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04  7:06 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
2010-08-04 12:26 ` Neil Horman
2010-08-05  6:40 ` Simon Horman [this message]

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=20100805064011.GB4630@verge.net.au \
    --to=horms@verge.net.au \
    --cc=andi@firstfloor.org \
    --cc=ebiederm@xmission.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikey@neuling.org \
    --cc=nhorman@redhat.com \
    --cc=torvalds@linux-foundation.org \
    --cc=xiyou.wangcong@gmail.com \
    /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
Powered by JetHome