From: "Daniel P. Berrangé" <berrange@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
"Peter Maydell" <peter.maydell@linaro.org>,
"Gustavo Romero" <gustavo.romero@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
qemu-arm@nongnu.org
Subject: Re: [PATCH 0/7] testing and misc updates (docker, ansible, .git*, gitlab)
Date: Wed, 1 Oct 2025 19:37:14 +0100 [thread overview]
Message-ID: <aN102hEBf6vny20l@redhat.com> (raw)
In-Reply-To: <4188260c-e8ac-9bea-5e05-6cd34c3e986d@eik.bme.hu>
On Wed, Oct 01, 2025 at 07:56:21PM +0200, BALATON Zoltan wrote:
> On Wed, 1 Oct 2025, Alex Bennée wrote:
> > My first set of patches for the development tree. Should be mostly
> > self-explanatory. We still need to apply the upstream COPYING patch
> > the u-boot-sam460ex code but we should decide if its worth mirroring
> > or should we just treat the copy as fully "ours".
>
> Which COPYING patch do you refer to? I have the upstream because when I
> submitted this I was told to do it this way instead of adding the u-boot
> sources to the QEMU tree. It can't be merged with the official u-boot used
> for e500 because it has sam460ex specific patches from the machine vendor
> which only supports this u-boot version. There are some updates from the
> vendor for real machine which I plan to add eventually but it's still based
> on an older u-boot version. With mirroring I can update upstream and send
> one patch to update the binary once it's mirrored, otherwise I'd need to
> send patches for each update and rely on somebody to merge them.
I opened this:
https://gitlab.com/qemu-project/u-boot-sam460ex/-/merge_requests/1
but then learnt u-boot-sam460ex is actually a mirror of your github
repo, and haven't got around to opening a new MR for your repo.
If you can pull the commits from that MR that'd be great, or I can
open a new MR, as you prefer.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-10-01 18:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 17:09 [PATCH 0/7] testing and misc updates (docker, ansible, .git*, gitlab) Alex Bennée
2025-10-01 17:09 ` [PATCH 1/7] .gitpublish: use origin/master as default base Alex Bennée
2025-10-01 17:09 ` [PATCH 2/7] .gitmodules: restore qemu-project mirror of u-boot Alex Bennée
2025-10-01 17:09 ` [PATCH 3/7] .gitmodules: restore qemu-project mirror of u-boot-sam460ex Alex Bennée
2025-10-01 17:09 ` [PATCH 4/7] tests/lcitool: drop 64 bit guests from i686 cross build Alex Bennée
2025-10-01 18:32 ` Marc-André Lureau
2025-10-01 18:41 ` Philippe Mathieu-Daudé
2025-10-01 20:49 ` Richard Henderson
2025-10-01 17:09 ` [PATCH 5/7] tests/lcitool: bump custom runner packages to Ubuntu 24.04 Alex Bennée
2025-10-01 20:50 ` Richard Henderson
2025-10-02 5:23 ` Thomas Huth
2025-10-02 5:24 ` Philippe Mathieu-Daudé
2025-10-01 17:09 ` [PATCH 6/7] gitlab: move custom runners " Alex Bennée
2025-10-01 20:52 ` Richard Henderson
2025-10-02 5:24 ` Thomas Huth
2025-10-02 5:25 ` Philippe Mathieu-Daudé
2025-10-01 17:09 ` [PATCH 7/7] scripts/ci: use recommended registration command Alex Bennée
2025-10-01 17:56 ` [PATCH 0/7] testing and misc updates (docker, ansible, .git*, gitlab) BALATON Zoltan
2025-10-01 18:37 ` Daniel P. Berrangé [this message]
2025-10-01 19:31 ` BALATON Zoltan
2025-10-01 21:51 ` Alex Bennée
2025-10-01 18:56 ` Alex Bennée
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=aN102hEBf6vny20l@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=gustavo.romero@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).