From: "Alex Bennée" <alex.bennee@linaro.org>
To: Brian Cain <brian.cain@oss.qualcomm.com>
Cc: qemu-devel@nongnu.org, ltaylorsimpson@gmail.com,
matheus.bernardino@oss.qualcomm.com,
marco.liebel@oss.qualcomm.com, quic_mburton@quicinc.com,
sid.manning@oss.qualcomm.com, ale@rev.ng, anjo@rev.ng,
berrange@redhat.com
Subject: Re: [PATCH v3 0/1] Update hexagon cross container to 22.1.0
Date: Wed, 04 Mar 2026 17:54:51 +0000 [thread overview]
Message-ID: <87o6l3o4yc.fsf@draig.linaro.org> (raw)
In-Reply-To: <87tsuvo509.fsf@draig.linaro.org> ("Alex Bennée"'s message of "Wed, 04 Mar 2026 17:53:42 +0000")
Alex Bennée <alex.bennee@linaro.org> writes:
> Brian Cain <brian.cain@oss.qualcomm.com> writes:
>
>> *** Note *** that this patch should not land without
>> "tests/tcg/multiarch/linux-test: use portable alternative for dirent64",
>> a newer musl present in this toolchain exposes this test issue.
>>
>> Changes in v3:
>> * change debian from 12->13
>
> Actually I meant to grab this one, but I get merge conflicts :-/
Conflicts with:
e2d4646a026 * tests/docker: upgrade most non-lcitool debian tests to debian 13
>
>
>>
>> Changes in v2:
>> * none -> v2 was unintentionally chosen for the first rev of
>> this patch. :(
>>
>> v2: https://lore.kernel.org/qemu-devel/20260303175444.1540049-1-brian.cain@oss.qualcomm.com/
>> v1: <none>
>>
>> Brian Cain (1):
>> tests/docker: Update hexagon cross toolchain to 22.1.0
>>
>> .../dockerfiles/debian-hexagon-cross.docker | 19 +++++++++++--------
>> 1 file changed, 11 insertions(+), 8 deletions(-)
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2026-03-04 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 21:05 [PATCH v3 0/1] Update hexagon cross container to 22.1.0 Brian Cain
2026-03-03 21:05 ` [PATCH v3 1/1] tests/docker: Update hexagon cross toolchain " Brian Cain
2026-03-04 14:51 ` Alex Bennée
2026-03-04 15:58 ` Brian Cain
2026-03-04 17:53 ` [PATCH v3 0/1] Update hexagon cross container " Alex Bennée
2026-03-04 17:54 ` Alex Bennée [this message]
2026-03-04 19:50 ` Brian Cain
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=87o6l3o4yc.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=ale@rev.ng \
--cc=anjo@rev.ng \
--cc=berrange@redhat.com \
--cc=brian.cain@oss.qualcomm.com \
--cc=ltaylorsimpson@gmail.com \
--cc=marco.liebel@oss.qualcomm.com \
--cc=matheus.bernardino@oss.qualcomm.com \
--cc=qemu-devel@nongnu.org \
--cc=quic_mburton@quicinc.com \
--cc=sid.manning@oss.qualcomm.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.