Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <jakubszczudlo40@gmail.com>, <openembedded-core@lists.openembedded.org>
Cc: "Hongxu Jia" <hongxu.jia@windriver.com>,
	"Yoann Congal" <yoann.congal@smile.fr>
Subject: Re: [OE-core] [scarthgap][PATCH] libgcrypt: upgrade 1.10.3 -> 1.10.4
Date: Wed, 08 Jul 2026 11:31:29 +0200	[thread overview]
Message-ID: <DJT32W69PZMH.3CI3ARE9YG46W@bootlin.com> (raw)
In-Reply-To: <20260707064301.32102-1-jakubszczudlo40@gmail.com>

On Tue Jul 7, 2026 at 8:43 AM CEST, Jakub Szczudlo via lists.openembedded.org wrote:
> Release notes are here:
> https://dev.gnupg.org/T8233.html
> Update contains fix for CVE-2026-41989 and because of building error patch need to be
> updated to fix compile flags in new version.
>
> Signed-off-by: Jakub Szczudlo <jakubszczudlo40@gmail.com>
> ---
> v3:
>  - Correct patch file name to be the same as patch title
> v2:
>  - Added new patch to fix building error with '-O2' in sysroot path for libgcrypt 1.10.4, patch
>    was taken from wrynose and backported.

Hi Jakub,

Thanks for your patch, but please remember to add the [scarthgap] prefix
in the subject when targeting stable branches.

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-07-08  9:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07  6:43 [PATCH] libgcrypt: upgrade 1.10.3 -> 1.10.4 Jakub Szczudlo
2026-07-08  9:31 ` Mathieu Dubois-Briand [this message]
2026-07-08  9:34   ` [OE-core] [scarthgap][PATCH] " Jakub Szczudlo
  -- strict thread matches above, loose matches on Subject: below --
2026-07-04 10:55 Jakub Szczudlo
2026-07-06 12:25 ` [OE-core] " Yoann Congal
2026-07-06 12:28   ` Jakub Szczudlo
2026-05-14 13:30 Guðni Már Gilbert
2026-06-09 11:51 ` [OE-core] " Jeremy Rosen

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=DJT32W69PZMH.3CI3ARE9YG46W@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=hongxu.jia@windriver.com \
    --cc=jakubszczudlo40@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yoann.congal@smile.fr \
    /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