meson.build | 22 +++++++++++++++++++--- target/arm/meson.build | 8 +++----- target/arm/tcg/meson.build | 2 +- 3 files changed, 23 insertions(+), 9 deletions(-)
The following changes since commit a85c588d07f8d3345ccad38b22026569a04571d1:
Merge tag 'pull-monitor-2026-05-05' of https://repo.or.cz/qemu/armbru into staging (2026-05-05 10:11:49 -0400)
are available in the Git repository at:
https://gitlab.com/p-b-o/qemu tags/pbouvier/pr/build_system-20260505
for you to fetch changes up to 2e44ff32fc758bf8c0df13b0287afb75bb00c38e:
target/arm: define stub library (2026-05-05 16:06:00 -0700)
----------------------------------------------------------------
Changes:
- [PATCH 0/2] single-binary: add stubs for target/ (Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>)
Link: https://lore.kernel.org/qemu-devel/20260424230103.1579600-1-pierrick.bouvier@oss.qualcomm.com
----------------------------------------------------------------
Pierrick Bouvier (2):
meson.build: define stubs library per target base architecture
target/arm: define stub library
meson.build | 22 +++++++++++++++++++---
target/arm/meson.build | 8 +++-----
target/arm/tcg/meson.build | 2 +-
3 files changed, 23 insertions(+), 9 deletions(-)
On Tue, May 5, 2026 at 7:07 PM Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com> wrote: > > The following changes since commit a85c588d07f8d3345ccad38b22026569a04571d1: > > Merge tag 'pull-monitor-2026-05-05' of https://repo.or.cz/qemu/armbru into staging (2026-05-05 10:11:49 -0400) > > are available in the Git repository at: > > https://gitlab.com/p-b-o/qemu tags/pbouvier/pr/build_system-20260505 > > for you to fetch changes up to 2e44ff32fc758bf8c0df13b0287afb75bb00c38e: > > target/arm: define stub library (2026-05-05 16:06:00 -0700) > > ---------------------------------------------------------------- > Changes: > - [PATCH 0/2] single-binary: add stubs for target/ (Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>) > Link: https://lore.kernel.org/qemu-devel/20260424230103.1579600-1-pierrick.bouvier@oss.qualcomm.com > > ---------------------------------------------------------------- > Pierrick Bouvier (2): > meson.build: define stubs library per target base architecture > target/arm: define stub library > > meson.build | 22 +++++++++++++++++++--- > target/arm/meson.build | 8 +++----- > target/arm/tcg/meson.build | 2 +- > 3 files changed, 23 insertions(+), 9 deletions(-) Is this a pull request for Paolo's build system tree? I'm not merging this directly because I prefer to follow MAINTAINERS so it's clear who sends pull requests for each subsystem. That way maintainers won't be surprised by me merging a pull request from another contributor who is not officially the maintainer and it's also better for security. Thanks, Stefan
Hi Stefan, Pierrick, On Wed, 6 May 2026 at 16:42, Stefan Hajnoczi <stefanha@gmail.com> wrote: > > On Tue, May 5, 2026 at 7:07 PM Pierrick Bouvier > <pierrick.bouvier@oss.qualcomm.com> wrote: > > > > The following changes since commit a85c588d07f8d3345ccad38b22026569a04571d1: > > > > Merge tag 'pull-monitor-2026-05-05' of https://repo.or.cz/qemu/armbru into staging (2026-05-05 10:11:49 -0400) > > > > are available in the Git repository at: > > > > https://gitlab.com/p-b-o/qemu tags/pbouvier/pr/build_system-20260505 > > > > for you to fetch changes up to 2e44ff32fc758bf8c0df13b0287afb75bb00c38e: > > > > target/arm: define stub library (2026-05-05 16:06:00 -0700) > > > > ---------------------------------------------------------------- > > Changes: > > - [PATCH 0/2] single-binary: add stubs for target/ (Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>) > > Link: https://lore.kernel.org/qemu-devel/20260424230103.1579600-1-pierrick.bouvier@oss.qualcomm.com > > > > ---------------------------------------------------------------- > > Pierrick Bouvier (2): > > meson.build: define stubs library per target base architecture > > target/arm: define stub library > > > > meson.build | 22 +++++++++++++++++++--- > > target/arm/meson.build | 8 +++----- > > target/arm/tcg/meson.build | 2 +- > > 3 files changed, 23 insertions(+), 9 deletions(-) > > Is this a pull request for Paolo's build system tree? > > I'm not merging this directly because I prefer to follow MAINTAINERS > so it's clear who sends pull requests for each subsystem. That way > maintainers won't be surprised by me merging a pull request from > another contributor who is not officially the maintainer and it's also > better for security. I did not notice Pierrick's PR and actually included these 2 commits in my latest "single-binary" pull request: https://lore.kernel.org/qemu-devel/20260506135524.20617-1-philmd@linaro.org/ Pierrick and I are simply reviewers on the "Build System" topic, but it happens that I send patches there where they are related to the overall single binary objective, and I see Pierrick as a co-maintainer in this area. However there is no clearly defined MAINTAINERS section, we happen to touch build system related files all over the tree. Regards, Phil.
On Wed, May 06, 2026 at 05:16:21PM +0200, Philippe Mathieu-Daudé wrote: > Hi Stefan, Pierrick, > > On Wed, 6 May 2026 at 16:42, Stefan Hajnoczi <stefanha@gmail.com> wrote: > > > > On Tue, May 5, 2026 at 7:07 PM Pierrick Bouvier > > <pierrick.bouvier@oss.qualcomm.com> wrote: > > > > > > The following changes since commit a85c588d07f8d3345ccad38b22026569a04571d1: > > > > > > Merge tag 'pull-monitor-2026-05-05' of https://repo.or.cz/qemu/armbru into staging (2026-05-05 10:11:49 -0400) > > > > > > are available in the Git repository at: > > > > > > https://gitlab.com/p-b-o/qemu tags/pbouvier/pr/build_system-20260505 > > > > > > for you to fetch changes up to 2e44ff32fc758bf8c0df13b0287afb75bb00c38e: > > > > > > target/arm: define stub library (2026-05-05 16:06:00 -0700) > > > > > > ---------------------------------------------------------------- > > > Changes: > > > - [PATCH 0/2] single-binary: add stubs for target/ (Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>) > > > Link: https://lore.kernel.org/qemu-devel/20260424230103.1579600-1-pierrick.bouvier@oss.qualcomm.com > > > > > > ---------------------------------------------------------------- > > > Pierrick Bouvier (2): > > > meson.build: define stubs library per target base architecture > > > target/arm: define stub library > > > > > > meson.build | 22 +++++++++++++++++++--- > > > target/arm/meson.build | 8 +++----- > > > target/arm/tcg/meson.build | 2 +- > > > 3 files changed, 23 insertions(+), 9 deletions(-) > > > > Is this a pull request for Paolo's build system tree? > > > > I'm not merging this directly because I prefer to follow MAINTAINERS > > so it's clear who sends pull requests for each subsystem. That way > > maintainers won't be surprised by me merging a pull request from > > another contributor who is not officially the maintainer and it's also > > better for security. > > I did not notice Pierrick's PR and actually included these 2 > commits in my latest "single-binary" pull request: > https://lore.kernel.org/qemu-devel/20260506135524.20617-1-philmd@linaro.org/ That can be fine, sometimes changes are cross-cutting or part of another sub-system (e.g. ARM target) even though they touch files a different subsystem. My concern is only about the pull request process. Please don't send pull requests with a new tag/branch name that is not in MAINTAINERS. No PR has ever been merged from Pierrick with a build_system-* tag and he is not listed in MAINTAINERS for Build System. This could be a sign that something in MAINTAINERS needs to be changed or it could be a sign that these patches should go through another tree (Paolo's or yours). > Pierrick and I are simply reviewers on the "Build System" topic, > but it happens that I send patches there where they are related to > the overall single binary objective, and I see Pierrick as a co-maintainer > in this area. However there is no clearly defined MAINTAINERS > section, we happen to touch build system related files all over > the tree. I can't accept random pull requests, even from regular contributors. Patches should go through subsystem maintainers listed in the MAINTAINERS file. This way we can be sure that only commits reviewed by a subsystem maintainers are merged and reduce the risk that malicious pull requests are merged (while I trust Pierrick, it lowers my guard if I'm accepting random pull requests from anyone at all). Stefan
On 5/6/2026 10:08 AM, Stefan Hajnoczi wrote: > On Wed, May 06, 2026 at 05:16:21PM +0200, Philippe Mathieu-Daudé wrote: >> Hi Stefan, Pierrick, >> >> On Wed, 6 May 2026 at 16:42, Stefan Hajnoczi <stefanha@gmail.com> wrote: >>> >>> On Tue, May 5, 2026 at 7:07 PM Pierrick Bouvier >>> <pierrick.bouvier@oss.qualcomm.com> wrote: >>>> >>>> The following changes since commit a85c588d07f8d3345ccad38b22026569a04571d1: >>>> >>>> Merge tag 'pull-monitor-2026-05-05' of https://repo.or.cz/qemu/armbru into staging (2026-05-05 10:11:49 -0400) >>>> >>>> are available in the Git repository at: >>>> >>>> https://gitlab.com/p-b-o/qemu tags/pbouvier/pr/build_system-20260505 >>>> >>>> for you to fetch changes up to 2e44ff32fc758bf8c0df13b0287afb75bb00c38e: >>>> >>>> target/arm: define stub library (2026-05-05 16:06:00 -0700) >>>> >>>> ---------------------------------------------------------------- >>>> Changes: >>>> - [PATCH 0/2] single-binary: add stubs for target/ (Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>) >>>> Link: https://lore.kernel.org/qemu-devel/20260424230103.1579600-1-pierrick.bouvier@oss.qualcomm.com >>>> >>>> ---------------------------------------------------------------- >>>> Pierrick Bouvier (2): >>>> meson.build: define stubs library per target base architecture >>>> target/arm: define stub library >>>> >>>> meson.build | 22 +++++++++++++++++++--- >>>> target/arm/meson.build | 8 +++----- >>>> target/arm/tcg/meson.build | 2 +- >>>> 3 files changed, 23 insertions(+), 9 deletions(-) >>> >>> Is this a pull request for Paolo's build system tree? >>> >>> I'm not merging this directly because I prefer to follow MAINTAINERS >>> so it's clear who sends pull requests for each subsystem. That way >>> maintainers won't be surprised by me merging a pull request from >>> another contributor who is not officially the maintainer and it's also >>> better for security. >> >> I did not notice Pierrick's PR and actually included these 2 >> commits in my latest "single-binary" pull request: >> https://lore.kernel.org/qemu-devel/20260506135524.20617-1-philmd@linaro.org/ > > That can be fine, sometimes changes are cross-cutting or part of another > sub-system (e.g. ARM target) even though they touch files a different > subsystem. > > My concern is only about the pull request process. Please don't send > pull requests with a new tag/branch name that is not in MAINTAINERS. No > PR has ever been merged from Pierrick with a build_system-* tag and he > is not listed in MAINTAINERS for Build System. > > This could be a sign that something in MAINTAINERS needs to be changed > or it could be a sign that these patches should go through another tree > (Paolo's or yours). > >> Pierrick and I are simply reviewers on the "Build System" topic, >> but it happens that I send patches there where they are related to >> the overall single binary objective, and I see Pierrick as a co-maintainer >> in this area. However there is no clearly defined MAINTAINERS >> section, we happen to touch build system related files all over >> the tree. > > I can't accept random pull requests, even from regular contributors. > Patches should go through subsystem maintainers listed in the > MAINTAINERS file. This way we can be sure that only commits reviewed by > a subsystem maintainers are merged and reduce the risk that malicious > pull requests are merged (while I trust Pierrick, it lowers my guard if > I'm accepting random pull requests from anyone at all). > That's totally my fault here, sorry. I have been assuming that "Build and test automation, general continuous integration" was by extension integrating build system, but it seems like it doesn't. I would not dare sending PR for an area I don't maintain officially. As well, in the past, Richard integrated some of those patches on build system for single-binary, but I appreciate that he's definitely more legitimate than me for pulling these kind of patches. Philippe and I will remove those patches, and I'll ping Paolo to let him pull this instead. > Stefan Regards, Pierrick
On Wed, May 06, 2026 at 10:45:07AM -0700, Pierrick Bouvier wrote: > On 5/6/2026 10:08 AM, Stefan Hajnoczi wrote: > > On Wed, May 06, 2026 at 05:16:21PM +0200, Philippe Mathieu-Daudé wrote: > >> Hi Stefan, Pierrick, > >> > >> On Wed, 6 May 2026 at 16:42, Stefan Hajnoczi <stefanha@gmail.com> wrote: > >>> > >>> On Tue, May 5, 2026 at 7:07 PM Pierrick Bouvier > >>> <pierrick.bouvier@oss.qualcomm.com> wrote: > >>>> > >>>> The following changes since commit a85c588d07f8d3345ccad38b22026569a04571d1: > >>>> > >>>> Merge tag 'pull-monitor-2026-05-05' of https://repo.or.cz/qemu/armbru into staging (2026-05-05 10:11:49 -0400) > >>>> > >>>> are available in the Git repository at: > >>>> > >>>> https://gitlab.com/p-b-o/qemu tags/pbouvier/pr/build_system-20260505 > >>>> > >>>> for you to fetch changes up to 2e44ff32fc758bf8c0df13b0287afb75bb00c38e: > >>>> > >>>> target/arm: define stub library (2026-05-05 16:06:00 -0700) > >>>> > >>>> ---------------------------------------------------------------- > >>>> Changes: > >>>> - [PATCH 0/2] single-binary: add stubs for target/ (Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>) > >>>> Link: https://lore.kernel.org/qemu-devel/20260424230103.1579600-1-pierrick.bouvier@oss.qualcomm.com > >>>> > >>>> ---------------------------------------------------------------- > >>>> Pierrick Bouvier (2): > >>>> meson.build: define stubs library per target base architecture > >>>> target/arm: define stub library > >>>> > >>>> meson.build | 22 +++++++++++++++++++--- > >>>> target/arm/meson.build | 8 +++----- > >>>> target/arm/tcg/meson.build | 2 +- > >>>> 3 files changed, 23 insertions(+), 9 deletions(-) > >>> > >>> Is this a pull request for Paolo's build system tree? > >>> > >>> I'm not merging this directly because I prefer to follow MAINTAINERS > >>> so it's clear who sends pull requests for each subsystem. That way > >>> maintainers won't be surprised by me merging a pull request from > >>> another contributor who is not officially the maintainer and it's also > >>> better for security. > >> > >> I did not notice Pierrick's PR and actually included these 2 > >> commits in my latest "single-binary" pull request: > >> https://lore.kernel.org/qemu-devel/20260506135524.20617-1-philmd@linaro.org/ > > > > That can be fine, sometimes changes are cross-cutting or part of another > > sub-system (e.g. ARM target) even though they touch files a different > > subsystem. > > > > My concern is only about the pull request process. Please don't send > > pull requests with a new tag/branch name that is not in MAINTAINERS. No > > PR has ever been merged from Pierrick with a build_system-* tag and he > > is not listed in MAINTAINERS for Build System. > > > > This could be a sign that something in MAINTAINERS needs to be changed > > or it could be a sign that these patches should go through another tree > > (Paolo's or yours). > > > >> Pierrick and I are simply reviewers on the "Build System" topic, > >> but it happens that I send patches there where they are related to > >> the overall single binary objective, and I see Pierrick as a co-maintainer > >> in this area. However there is no clearly defined MAINTAINERS > >> section, we happen to touch build system related files all over > >> the tree. > > > > I can't accept random pull requests, even from regular contributors. > > Patches should go through subsystem maintainers listed in the > > MAINTAINERS file. This way we can be sure that only commits reviewed by > > a subsystem maintainers are merged and reduce the risk that malicious > > pull requests are merged (while I trust Pierrick, it lowers my guard if > > I'm accepting random pull requests from anyone at all). > > > > That's totally my fault here, sorry. > > I have been assuming that "Build and test automation, general continuous > integration" was by extension integrating build system, but it seems > like it doesn't. I would not dare sending PR for an area I don't > maintain officially. > > As well, in the past, Richard integrated some of those patches on build > system for single-binary, but I appreciate that he's definitely more > legitimate than me for pulling these kind of patches. > > Philippe and I will remove those patches, and I'll ping Paolo to let him > pull this instead. Including the patches in Philippe's pull request is probably fine as long as they are not something that Paolo needs to review. Sometimes files outside the subsystem are touched in a pull request and that's okay. My concern is only that each pull request email series should come from someone listed as maintainer for that area. For example, if I send a migration pull request and then Peter or Richard would probably be confused because I'm not the maintainer. Stefan
© 2016 - 2026 Red Hat, Inc.