From: akuster808 <akuster808@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Alex.Gonzalez@digi.com
Cc: poky@yoctoproject.org
Subject: Re: [poky] [rocko] Backport request for meta/recipes-kernel/cryptodev
Date: Sat, 6 Oct 2018 09:02:25 -0700 [thread overview]
Message-ID: <54e188df-f109-3e56-c154-d8b42e206480@gmail.com> (raw)
In-Reply-To: <982a032d-362e-cc1a-c84d-2496a0a21171@windriver.com>
On 10/05/2018 01:49 PM, Randy MacLeod wrote:
> Hi Alex,
>
> Armin maintains the rocko branch so best to CC him.
>
> Also, I've moved this to the oe-core list where
> we handle oe-core commits. Poky is composed of
> several layers to make things easier to build
> but we use the other email lists for development.
>
> Armin,
>
> This is a simple patch and I was able
> to cherry-pick the corresponding oe-core commit:
>
> 270a1e9bcf26a43f5cbdc5b901c4c6f79495311d
>
> back to rocko-next, and then run:
> bitbake -c patch linux-yocto.
> The change is a no-op for the standard rocko kernel so that's
> all I did to test (actually, I'm starting a linux-yocto build
> but I'd be shocked if it failed).
>
> Will you add this to your rocko-next queue or
> would you like Alex to re-submit following the guidelines:
> http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
>
Thanks Randy,
its in my queue.
- armin
>
> ../Randy
>
>
> On 10/05/2018 08:00 AM, Gonzalez, Alex wrote:
>> Hi,
>>
>> Could you please backport commit
>> c568e89c3d316e5c10369c6ff48e871828bad783 to
>> rocko?
>>
>> https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=c568e89c3d316e5c10369c6ff48e871828bad783
>>
>>
>> This will allow to build cryptodev with kernels >= 4.17.
>>
>> Thanks,
>> Alex
>>
>
>
prev parent reply other threads:[~2018-10-06 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181005120055.GC7228@agonzal-linux>
2018-10-05 20:49 ` [poky] [rocko] Backport request for meta/recipes-kernel/cryptodev Randy MacLeod
2018-10-06 16:02 ` akuster808 [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=54e188df-f109-3e56-c154-d8b42e206480@gmail.com \
--to=akuster808@gmail.com \
--cc=Alex.Gonzalez@digi.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.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