From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] lzop: Fix build using x32 ABI
Date: Thu, 26 Mar 2015 08:37:43 -0600 [thread overview]
Message-ID: <551419B7.3080201@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LbsqWcoddvK+xs=u0QQ7rDsn7=9eh5j+o2=KtP-v2MUDw@mail.gmail.com>
On 26/03/15 06:45, Burton, Ross wrote:
> On 25 March 2015 at 22:26, Aníbal Limón <anibal.limon@linux.intel.com>
> wrote:
>
>> +PR = "r1"
>>
> No need to add a PR.
Hi Ross,
I followed the documentation [1], if no increment PR is needed i think
we need to clarity in the docs.
Sending v2...
[1]
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#using-a-quilt-workflow
alimon
>
> Ross
>
next prev parent reply other threads:[~2015-03-26 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 22:26 [PATCH] lzop: Fix build using x32 ABI Aníbal Limón
2015-03-26 12:45 ` Burton, Ross
2015-03-26 14:37 ` Aníbal Limón [this message]
2015-03-26 14:40 ` Burton, Ross
2015-03-26 14:42 ` Burton, Ross
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=551419B7.3080201@linux.intel.com \
--to=anibal.limon@linux.intel.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