All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: "Maxin B. John" <maxin.john@intel.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] kexec: update supported architecture list
Date: Tue, 19 Jan 2016 17:30:05 +0800	[thread overview]
Message-ID: <569E021D.3070501@windriver.com> (raw)
In-Reply-To: <1448873637-23617-1-git-send-email-maxin.john@intel.com>

On 2015年11月30日 16:53, Maxin B. John wrote:
> Now, kexec is supported in mips, aarch64 and most of the machines within
> powerpc family. So, remove those architecture specific restrictions.
>
> Signed-off-by: Maxin B. John <maxin.john@intel.com>
> ---
>   meta/recipes-core/packagegroups/packagegroup-core-tools-testapps.bb | 6 +-----
>   1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/meta/recipes-core/packagegroups/packagegroup-core-tools-testapps.bb b/meta/recipes-core/packagegroups/packagegroup-core-tools-testapps.bb
> index 95b3988..acbae11 100644
> --- a/meta/recipes-core/packagegroups/packagegroup-core-tools-testapps.bb
> +++ b/meta/recipes-core/packagegroups/packagegroup-core-tools-testapps.bb
> @@ -11,13 +11,9 @@ PACKAGE_ARCH = "${MACHINE_ARCH}"
>   
>   inherit packagegroup
>   
> -# kexec-tools doesn't work on Mips
> +# kexec-tools doesn't work on e5500-64b yet
>   KEXECTOOLS ?= "kexec"
> -KEXECTOOLS_mips ?= ""
> -KEXECTOOLS_mipsel ?= ""
> -KEXECTOOLS_powerpc ?= ""
>   KEXECTOOLS_e5500-64b ?= ""
> -KEXECTOOLS_aarch64 ?= ""
>   
>   X11GLTOOLS = "\
>       mesa-demos \

May I ask why this patch didn't be merged?


-- 
Regards,
Neil | Kai Kang



      reply	other threads:[~2016-01-19  9:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30  8:53 [PATCH] kexec: update supported architecture list Maxin B. John
2016-01-19  9:30 ` Kang Kai [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=569E021D.3070501@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=maxin.john@intel.com \
    --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 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.