From: Andi Kleen <andi@firstfloor.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Michael Neuling <mikey@neuling.org>,
Simon Horman <horms@verge.net.au>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [rfc] Merge kexec-tools into the kernel tree
Date: Wed, 04 Aug 2010 17:05:08 +0200 [thread overview]
Message-ID: <87bp9ie7vf.fsf@basil.nowhere.org> (raw)
In-Reply-To: <m17hk6de62.fsf@fess.ebiederm.org> (Eric W. Biederman's message of "Wed, 04 Aug 2010 00:34:29 -0700")
ebiederm@xmission.com (Eric W. Biederman) writes:
>
> I'm afraid that someone has a good answer for why their lives would be
> simpler if /sbin/kexec was in the kernel tree and I will be absolutely
> horrified and about someones stupidity when I hear that answer.
Same here. In fact I guess it would be counter productive: it would
discourage a stable API between the kernel and the user tool.
We're seeing this problem with other user tools which are in
the kernel tree.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: Simon Horman <horms@verge.net.au>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Michael Neuling <mikey@neuling.org>
Subject: Re: [rfc] Merge kexec-tools into the kernel tree
Date: Wed, 04 Aug 2010 17:05:08 +0200 [thread overview]
Message-ID: <87bp9ie7vf.fsf@basil.nowhere.org> (raw)
In-Reply-To: <m17hk6de62.fsf@fess.ebiederm.org> (Eric W. Biederman's message of "Wed, 04 Aug 2010 00:34:29 -0700")
ebiederm@xmission.com (Eric W. Biederman) writes:
>
> I'm afraid that someone has a good answer for why their lives would be
> simpler if /sbin/kexec was in the kernel tree and I will be absolutely
> horrified and about someones stupidity when I hear that answer.
Same here. In fact I guess it would be counter productive: it would
discourage a stable API between the kernel and the user tool.
We're seeing this problem with other user tools which are in
the kernel tree.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-08-04 15:05 UTC|newest]
Thread overview: 24+ 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:06 ` Simon Horman
2010-08-04 7:22 ` Américo Wang
2010-08-04 7:22 ` Américo Wang
2010-08-04 7:34 ` Eric W. Biederman
2010-08-04 7:34 ` Eric W. Biederman
2010-08-04 15:05 ` Andi Kleen [this message]
2010-08-04 15:05 ` Andi Kleen
2010-08-04 23:11 ` Michael Neuling
2010-08-04 23:11 ` Michael Neuling
2010-08-05 0:04 ` Eric W. Biederman
2010-08-05 0:04 ` Eric W. Biederman
2010-08-05 1:19 ` Michael Neuling
2010-08-05 1:19 ` Michael Neuling
2010-08-05 3:26 ` Américo Wang
2010-08-05 3:26 ` Américo Wang
2010-08-05 3:22 ` Américo Wang
2010-08-05 3:22 ` Américo Wang
2010-08-04 8:08 ` Bernhard Walle
2010-08-04 8:08 ` Bernhard Walle
2010-08-04 12:26 ` Neil Horman
2010-08-04 12:26 ` Neil Horman
2010-08-05 6:40 ` Simon 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=87bp9ie7vf.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.