From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: mathieu.dubois-briand@bootlin.com,
openembedded-core@lists.openembedded.org
Cc: michael.opdenacker@rootcommit.com,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Jennifer Chukwu <jennifer.chukwu@amarulasolutions.com>
Subject: Re: [OE-core] [PATCH 6/9] acpica: upgrade 20260408 -> 20260930
Date: Fri, 2 Oct 2026 09:51:19 +0200 [thread overview]
Message-ID: <6905022a-cdb2-460e-9bab-53b352149463@rootcommit.com> (raw)
In-Reply-To: <20261002-mathieu-2026-10-01-upgrades-v1-6-3fdeab391403@bootlin.com>
Hi Mathieu
Thanks for the patch!
On 10/2/26 9:36 AM, Mathieu Dubois-Briand via lists.openembedded.org wrote:
> --- /dev/null
> +++ b/meta/recipes-extended/acpica/acpica_20260930.bb
> @@ -0,0 +1,345 @@
> +# FIXME: the LIC_FILES_CHKSUM values have been updated by 'devtool upgrade'.
> +# The following is the difference between the old and the new license text.
> +# Please update the LICENSE value if needed, and summarize the changes in
> +# the commit message via 'License-Update:' tag.
> +# (example: 'License-Update: copyright years updated.')
You forgot to remove the FIXME section ;)
By the way, Jennifer Chukwu sent another patch for the same update
yesterday. Your patch has a better summary of upstream changes but hers
doesn't have this problem...
Thanks
Michael.
next prev parent reply other threads:[~2026-10-02 7:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 7:36 [PATCH 0/9] 2026-10-01 upgrades Mathieu Dubois-Briand
2026-10-02 7:36 ` [PATCH 1/9] python3-uv-build: upgrade 0.12.19 -> 0.12.21 Mathieu Dubois-Briand
2026-10-02 7:36 ` [PATCH 2/9] python3-git: upgrade 3.1.62 -> 3.2.0 Mathieu Dubois-Briand
2026-10-02 7:36 ` [PATCH 3/9] python3-cryptography,python3-cryptography-vectors: upgrade 50.0.1 -> 50.0.2 Mathieu Dubois-Briand
2026-10-02 7:36 ` [PATCH 4/9] python3-pdm-backend: upgrade 2.4.10 -> 2.5.0 Mathieu Dubois-Briand
2026-10-02 7:36 ` [PATCH 5/9] harfbuzz: upgrade 14.5.0 -> 14.5.1 Mathieu Dubois-Briand
2026-10-02 7:36 ` [PATCH 6/9] acpica: upgrade 20260408 -> 20260930 Mathieu Dubois-Briand
2026-10-02 7:51 ` Michael Opdenacker [this message]
2026-10-02 9:59 ` [OE-core] " Mathieu Dubois-Briand
2026-10-02 7:36 ` [PATCH 7/9] libmd: upgrade 1.2.0 -> 1.3.0 Mathieu Dubois-Briand
2026-10-02 7:36 ` [PATCH 8/9] spirv-llvm-translator: upgrade 23.1.1 -> 23.1.2 Mathieu Dubois-Briand
2026-10-02 7:36 ` [PATCH 9/9] ltp: upgrade 20260529 -> 20260930 Mathieu Dubois-Briand
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=6905022a-cdb2-460e-9bab-53b352149463@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=jennifer.chukwu@amarulasolutions.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=thomas.petazzoni@bootlin.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