public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>, Saul Wold <sgw@linux.intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/6] cryptodev: 1.8 -> 1.9
Date: Thu, 13 Jul 2017 10:51:09 +0800	[thread overview]
Message-ID: <a75792ff-4291-1f5c-dca3-0a97ce64639b@windriver.com> (raw)
In-Reply-To: <CAJTo0LanadueCFtjEZXDrk3-jkv2+Y3kBO6FsSBC-9t-Ey1GWg@mail.gmail.com>



On 07/12/2017 09:39 PM, Burton, Ross wrote:
> Oh, didn't notice that.  Not sure I want to know why meta-intel has to patch
> cryptodev!
>
> CCing Saul for his input.

I've sent a patch to meta-intel@yoctoproject.org to update the patch.
If a layer has a bbappend and it patches the source, I usually prefer
not using wildcard as the version:

cryptodev-module_%.bbappend

And also set BB_DANGLINGAPPENDS_WARNONLY in layer.conf during development,
then we can have time to fix the errors.

BTW, I sent a meta-gplv2 patch to poky@yoctoproject.org two days ago, but
I didn't find it in poky@yoctoproject.org, Ross, did you see it, please ?
Maybe I should send it again.


// Robert

>
> Ross
>
> On 12 July 2017 at 14:36, Robert Yang <liezhi.yang@windriver.com
> <mailto:liezhi.yang@windriver.com>> wrote:
>
>
>
>     On 07/12/2017 08:32 PM, Burton, Ross wrote:
>
>         ERROR: cryptodev-module-1.9-r0 do_patch: Command Error: 'quilt --quiltrc
>         /data/poky-tmp/master/work/intel_corei7_64-poky-linux/cryptodev-module/1.9-r0/recipe-sysroot-native/etc/quiltrc
>         push' exited with 0  Output:
>         Applying patch 0001-zc-Force-4.10-get_user_pages_remote-API.patch
>         patching file zc.c
>         Hunk #1 FAILED at 67.
>         1 out of 1 hunk FAILED -- rejects in file zc.c
>         Patch 0001-zc-Force-4.10-get_user_pages_remote-API.patch does not apply
>         (enforce
>         with -f)
>
>
>     This patch is from meta-intel which I didn't build, sorry, I will fix it.
>
>     // Robert
>
>
>
>         Ross
>
>


  reply	other threads:[~2017-07-13  2:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12 10:15 [PATCH 0/6] Packages Upgrade Robert Yang
2017-07-12 10:15 ` [PATCH 1/6] automake: 1.15 -> 1.15.1 Robert Yang
2017-07-12 10:15 ` [PATCH 2/6] cryptodev: 1.8 -> 1.9 Robert Yang
2017-07-12 12:32   ` Burton, Ross
2017-07-12 13:36     ` Robert Yang
2017-07-12 13:39       ` Burton, Ross
2017-07-13  2:51         ` Robert Yang [this message]
2017-07-13  9:50           ` Burton, Ross
2017-07-13 10:03             ` Robert Yang
2017-07-15 13:13               ` Khem Raj
2017-07-18 18:54                 ` Denys Dmytriyenko
2017-07-20 15:14                   ` Burton, Ross
2017-07-18  8:45               ` Paul Eggleton
2017-07-18  8:48                 ` Robert Yang
2017-07-12 10:15 ` [PATCH 3/6] debianutils: 4.8.1 -> 4.8.1.1 Robert Yang
2017-07-12 10:15 ` [PATCH 4/6] git: 2.11.1 -> 2.13.2 Robert Yang
2017-07-12 15:38   ` Leonardo Sandoval
2017-07-13  2:55     ` Robert Yang
2017-07-13 12:50       ` Jose Lamego
2017-07-12 10:15 ` [PATCH 5/6] gnu-efi: 3.0.5 -> 3.0.6 Robert Yang
2017-07-12 10:15 ` [PATCH 6/6] libbsd: 0.8.3 -> 0.8.5 Robert Yang
2017-07-13  9:40   ` Burton, Ross
2017-07-13  9:45     ` Burton, Ross
2017-07-13 11:10       ` Robert Yang
2017-07-13 13:32         ` Khem Raj

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=a75792ff-4291-1f5c-dca3-0a97ce64639b@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    --cc=sgw@linux.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