From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Marko, Peter" <Peter.Marko@siemens.com>,
"Hongxu Jia" <hongxu.jia@windriver.com>,
"alex.kanavin@gmail.com" <alex.kanavin@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/5] libxml2: upgrade 2.13.8 -> 2.14.3
Date: Thu, 22 May 2025 14:25:06 +0200 [thread overview]
Message-ID: <DA2ORDMJAWTX.2XH4RND735F7C@bootlin.com> (raw)
In-Reply-To: <AS1PR10MB5697DC8D007471A68D8709ECFD99A@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM>
On Thu May 22, 2025 at 2:14 PM CEST, Peter Marko wrote:
>
> OK, I have updated my patch to .3 and sent to mailing list.
> Don't forget to pick the lttng-tools patch again with it...
>
> Peter
>
Thanks, I will take both patches for my next build.
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-05-22 12:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 8:09 [PATCH 1/5] libxml2: upgrade 2.13.8 -> 2.14.3 Hongxu Jia
2025-05-21 8:09 ` [PATCH v2 2/5] patch: upgrade 2.7.6 -> 2.8 Hongxu Jia
2025-05-21 8:09 ` [PATCH v2 3/5] man-pages: upgrade 6.13 -> 6.14 Hongxu Jia
2025-05-21 8:09 ` [PATCH v2 4/5] libgcrypt: upgrade 1.11.0 -> 1.11.1 Hongxu Jia
2025-05-21 8:09 ` [PATCH 5/5] lttng-tools: fix compile failed with libxml2 2.14.0+ Hongxu Jia
2025-05-22 6:30 ` [PATCH 1/5] libxml2: upgrade 2.13.8 -> 2.14.3 Mathieu Dubois-Briand
2025-05-22 6:35 ` Marko, Peter
2025-05-22 8:58 ` Mathieu Dubois-Briand
2025-05-22 12:14 ` Marko, Peter
2025-05-22 12:25 ` Mathieu Dubois-Briand [this message]
2025-05-26 1:55 ` [OE-core] " Khem Raj
2025-05-26 17:48 ` Marko, Peter
2025-05-26 18:57 ` Khem Raj
2025-05-26 19:36 ` Marko, Peter
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=DA2ORDMJAWTX.2XH4RND735F7C@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=Peter.Marko@siemens.com \
--cc=alex.kanavin@gmail.com \
--cc=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.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