Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] packagegroup-core-tools-testapps: disable kexec for mips64 and mis64n32
Date: Fri, 4 Dec 2015 10:17:10 +0800	[thread overview]
Message-ID: <5660F7A6.8070102@windriver.com> (raw)
In-Reply-To: <CAJTo0Lb0qXpx0RL23XCfrh3JV_pDnDrENWyoyoehQTX6uNhqoA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 911 bytes --]

On 2015年12月03日 22:13, Burton, Ross wrote:
>
> On 3 December 2015 at 06:32, <kai.kang@windriver.com 
> <mailto:kai.kang@windriver.com>> wrote:
>
>     @@ -15,6 +15,8 @@ inherit packagegroup
>      KEXECTOOLS ?= "kexec"
>      KEXECTOOLS_mips ?= ""
>      KEXECTOOLS_mipsel ?= ""
>     +KEXECTOOLS_mips64 ?= ""
>     +KEXECTOOLS_mips64n32 ?= ""
>      KEXECTOOLS_powerpc ?= ""
>      KEXECTOOLS_e5500-64b ?= ""
>      KEXECTOOLS_aarch64 ?= ""
>
>
> I've rebased this on top of Maxin's patch that removed many of these 
> exclusions (mips, mipsel, powerpc, aarch64), but could you confirm 
> that is the right thing to do?

Hi Ross,

I didn't find Maxin's patch on oe-core list. I double check with our bsp 
guy that kexec supports mips now but may need extra drivers  for each board.

So please ignore this patch.

Thanks,
Kai

>
> Ross


-- 
Regards,
Neil | Kai Kang


[-- Attachment #2: Type: text/html, Size: 2419 bytes --]

      reply	other threads:[~2015-12-04  2:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-03  6:32 [PATCH 0/1] packagegroup-core-tools-testapps:disable kexec for for mips64 and mis64n32 kai.kang
2015-12-03  6:32 ` [PATCH 1/1] packagegroup-core-tools-testapps: disable kexec " kai.kang
2015-12-03 14:13   ` Burton, Ross
2015-12-04  2:17     ` 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=5660F7A6.8070102@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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