Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3 1/1] package/acpica: bump to version 20230628
Date: Thu, 27 Jul 2023 12:35:37 +0200	[thread overview]
Message-ID: <20230727123537.4039db96@windsurf> (raw)
In-Reply-To: <20230725213609.19784-1-ju.o@free.fr>

On Tue, 25 Jul 2023 23:36:09 +0200
Julien Olivain <ju.o@free.fr> wrote:

> For change log since 20220331, see:
> - https://github.com/acpica/acpica/blob/R06_28_23/documents/changes.txt
> 
> This commit also drop the patch removing -Werror in CFLAGS, as an
> alternative is now available upstream, merged in [1]. This commit is
> included in release 20221020. The build commands are updated
> accordingly to set the new NOWERROR=TRUE option to achieve the same
> behavior.
> 
> With the patch removal, .checkpackageignore is also updated
> accordingly.
> 
> Upstream commit [2] also introduced a use of wcslen() and <wchar.h>.
> This commit was first included in tag R10_20_22 (version 20221020).
> Therefore, this new version need wchar. The new depedency is added.
> 
> The _SOURCE file is also changed from acpica-unix2 to acpica-unix,
> as the current acpica download page at [3] shows:
> 
> """
> Note: The unix2 source package is deprecated since the dual license is
> now included in all source modules (along with the Intel
> license). This package will be removed from future ACPICA releases.
> """
> 
> The _SITE url is also updated to the new download link, since the
> acpica website now redirects to Intel:
> 
>     curl -si https://www.acpica.org | grep Location:
>     Location: https://www.intel.com/content/www/us/en/developer/topic-technology/open/acpica/overview.html
> 
> The license file hash is also updated, due to the copyright year
> update. It is also worth mentioning that the files in the new archive
> have three alternative licenses in their headers: Intel, BSD-3-Clause
> and GPL-2.0.
> 
> Finally, since a SHA1 hash is published on the download page, it is
> added to the hash file.
> 
> This version bump is motivated by the introduction of RISC-V related
> definitions.
> 
> [1] https://github.com/acpica/acpica/commit/3fd0f940408fc01a2c52c5be5f2beb0218a3d907
> [2] https://github.com/acpica/acpica/commit/cd6a30897593f6052abf0b9a791671dcf07b9596
> [3] https://www.intel.com/content/www/us/en/developer/topic-technology/open/acpica/download.html
> 
> Cc: Erico Nunes <nunes.erico@gmail.com>
> Signed-off-by: Julien Olivain <ju.o@free.fr>

Thanks a lot for the super extensive commit message, this is very, very
good as it clarifies all changes making the review extremely easy.

Applied to master, of course!

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-07-27 10:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 21:36 [Buildroot] [PATCH v3 1/1] package/acpica: bump to version 20230628 Julien Olivain
2023-07-27 10:35 ` Thomas Petazzoni via buildroot [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=20230727123537.4039db96@windsurf \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --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