Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: wangmy <wangmy@fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] cryptodev-linux: upgrade 1.12 -> 1.13
Date: Mon, 10 Apr 2023 19:27:45 +0200	[thread overview]
Message-ID: <2023041017274515a16a50@mail.local> (raw)
In-Reply-To: <1681116997-24685-4-git-send-email-wangmy@fujitsu.com>


ERROR: cryptodev-module-1.12-r0 do_patch: QA Issue: Fuzz detected:
Applying patch 0001-Disable-installing-header-file-provided-by-another-p.patch
patching file Makefile
Hunk #1 succeeded at 36 with fuzz 2 (offset 3 lines).
The context lines in the patches can be updated with devtool:
    devtool modify cryptodev-module
    devtool finish --force-patch-refresh cryptodev-module <layer_path>
Don't forget to review changes done by devtool!
Patch log indicates that patches do not apply cleanly. [patch-fuzz]
ERROR: cryptodev-module-1.12-r0 do_patch: Fatal QA errors were found, failing task.

On 10/04/2023 16:56:36+0800, wangmy wrote:
> From: Wang Mingyu <wangmy@fujitsu.com>
> 
> Changelog:
> ==========
> * Fix compilation issues against Linux kernel 6.3
> * Add support for xts, cfb, ofb and ccm aes algorithms
> * Fix for a potential issue with CIOCCPHASH
> * clean-up and maintenance
> 
> Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
> ---
>  .../{cryptodev-linux_1.12.bb => cryptodev-linux_1.13.bb}        | 0
>  meta/recipes-kernel/cryptodev/cryptodev.inc                     | 2 +-
>  2 files changed, 1 insertion(+), 1 deletion(-)
>  rename meta/recipes-kernel/cryptodev/{cryptodev-linux_1.12.bb => cryptodev-linux_1.13.bb} (100%)
> 
> diff --git a/meta/recipes-kernel/cryptodev/cryptodev-linux_1.12.bb b/meta/recipes-kernel/cryptodev/cryptodev-linux_1.13.bb
> similarity index 100%
> rename from meta/recipes-kernel/cryptodev/cryptodev-linux_1.12.bb
> rename to meta/recipes-kernel/cryptodev/cryptodev-linux_1.13.bb
> diff --git a/meta/recipes-kernel/cryptodev/cryptodev.inc b/meta/recipes-kernel/cryptodev/cryptodev.inc
> index ef342a157c..61c688f1d0 100644
> --- a/meta/recipes-kernel/cryptodev/cryptodev.inc
> +++ b/meta/recipes-kernel/cryptodev/cryptodev.inc
> @@ -10,7 +10,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>  
>  SRC_URI = "git://github.com/cryptodev-linux/cryptodev-linux;branch=master;protocol=https \
>             "
> -SRCREV = "e0c25e289d6baf1d83c2b9cb523d3bc237d0c0c9"
> +SRCREV = "795f5fda1485d447cdbad342e8304be317d4f7e8"
>  
>  S = "${WORKDIR}/git"
>  
> -- 
> 2.34.1
> 

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#179846): https://lists.openembedded.org/g/openembedded-core/message/179846
> Mute This Topic: https://lists.openembedded.org/mt/98171941/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2023-04-10 17:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10  8:56 [OE-core] [PATCH] apr: upgrade 1.7.2 -> 1.7.3 wangmy
2023-04-10  8:56 ` [OE-core] [PATCH] bind: upgrade 9.18.12 -> 9.18.13 wangmy
2023-04-10  8:56 ` [OE-core] [PATCH] cracklib: upgrade 2.9.10 -> 2.9.11 wangmy
2023-04-10  8:56 ` [OE-core] [PATCH] cryptodev-linux: upgrade 1.12 -> 1.13 wangmy
2023-04-10 17:27   ` Alexandre Belloni [this message]
2023-04-10  8:56 ` [OE-core] [PATCH] dnf: upgrade 4.14.0 -> 4.15.0 wangmy
2023-04-11  1:50   ` Alexandre Belloni

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=2023041017274515a16a50@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=wangmy@fujitsu.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