Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] kexec-tools: don't depend on virtual/kernel
Date: Thu, 09 Jun 2011 15:43:01 +0100	[thread overview]
Message-ID: <1307630581.15712.162.camel@rex> (raw)
In-Reply-To: <1307620723.2529.4861.camel@phil-desktop>

On Thu, 2011-06-09 at 12:58 +0100, Phil Blundell wrote:
> There doesn't appear to be any terribly good reason for kexec-tools to
> depend on the kernel.  (I verified that kexec-tools is buildable in a
> clean TMPDIR without having previously built virtual/kernel.)  
> 
> Having this dependency in place is a nuisance because it makes it
> awkward to put kexec into an initramfs.  So, it seems like we would be
> better off without.
> 
> Signed-off-by: Phil Blundell <philb@gnu.org>
> ---
>  meta/recipes-kernel/kexec/kexec-tools.inc |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)

Merged to master, thanks.

Richard




      reply	other threads:[~2011-06-09 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 11:58 [PATCH] kexec-tools: don't depend on virtual/kernel Phil Blundell
2011-06-09 14:43 ` Richard Purdie [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=1307630581.15712.162.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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