From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: buildroot@buildroot.org, linux-amarula@amarulasolutions.com
Subject: Re: [Buildroot] [PATCH 1/2] package/acpica: switch to github
Date: Wed, 23 Oct 2024 23:15:45 +0200 [thread overview]
Message-ID: <20241023231545.092e14df@windsurf> (raw)
In-Reply-To: <20241008202609.3832478-1-dario.binacchi@amarulasolutions.com>
On Tue, 8 Oct 2024 22:26:08 +0200
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:
> As reported in [1] the traditional acpica.org website releases might get
> delayed due to website publication process, and indeed, on GitHub, the
> latest released version is 20240927, while in [2] the 20240827 version
> appears. Furthermore, in [2], explicit reference is made to the GitHub
> URL for direct access to the public ACPICA git repository.
>
> [1] https://github.com/acpica/acpica/releases
> [2] https://www.intel.com/content/www/us/en/developer/topic-technology/open/acpica/download.html
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> ---
> package/acpica/acpica.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Both applied to master, 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
prev parent reply other threads:[~2024-10-23 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 20:26 [Buildroot] [PATCH 1/2] package/acpica: switch to github Dario Binacchi
2024-10-08 20:26 ` [Buildroot] [PATCH 2/2] package/acpica: bump to version 20240927 Dario Binacchi
2024-10-23 21:15 ` 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=20241023231545.092e14df@windsurf \
--to=buildroot@buildroot.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.