Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: gpe-scap-1.3 patch for mipsel target
Date: Tue, 10 Mar 2009 19:58:14 -0700	[thread overview]
Message-ID: <200903101958.18551.raj.khem@gmail.com> (raw)
In-Reply-To: <180e2c240903101840j87d5ce6w1d1af520b488eab4@mail.gmail.com>

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

On Tuesday 10 March 2009 18:40:55 yajin zhou wrote:
> Hi everyone, I reported this bug in bug tracker but got no response. So I
> post it here again.
>
> http://bugs.openembedded.net/show_bug.cgi?id=5061
>
> The gpe scap version 1.3 has a bug to be built for mips target. The patch
> is here. http://bugs.openembedded.net/attachment.cgi?id=13835

Looks ok to me. Except you might want to generate a -p1 diff and bump up the PR

Thx

-- 
Khem Raj

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 204 bytes --]

  reply	other threads:[~2009-03-11  2:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11  1:40 gpe-scap-1.3 patch for mipsel target yajin zhou
2009-03-11  2:58 ` Khem Raj [this message]
2009-03-11 10:03 ` Florian Boor

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=200903101958.18551.raj.khem@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@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