From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Stefan Agner <stefan@agner.ch>
Cc: kaszak@gmail.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/openvmtools: bump version to 11.3.5
Date: Wed, 1 Jun 2022 23:54:48 +0200 [thread overview]
Message-ID: <20220601235448.59de7f7e@windsurf> (raw)
In-Reply-To: <9e9f78237f6f8ab0ee9e235b5b1c4b47ac1ea560.1652945312.git.stefan@agner.ch>
Hello Stefan,
On Thu, 19 May 2022 09:29:06 +0200
Stefan Agner <stefan@agner.ch> wrote:
> Rebase patches as necessary and bump version to 11.3.5. This allows
> to build openvmtools for aarch64.
If this version bump allows to build openvmtools for aarch64, then any
reason to not enable openvmtools on aarch64 as part of this commit?
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-06-01 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 7:29 [Buildroot] [PATCH v2] package/openvmtools: bump version to 11.3.5 Stefan Agner
2022-06-01 21:54 ` 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=20220601235448.59de7f7e@windsurf \
--to=buildroot@buildroot.org \
--cc=kaszak@gmail.com \
--cc=stefan@agner.ch \
--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