Question on backporting. [Was Re: [PATCH v2 2/2] powerpc: Add HWCAP3/HWCAP4 data to TCB for Power Architecture.]

[Tulio Magno Quites Machado Filho]

Peter Bergner <bergner@linux.ibm.com> writes:

> As someone new to the Power maintainership role, can someone help explain
> the process/rules for backporting changes into the release branches?

I like the explanation from this section of the wiki:
https://sourceware.org/glibc/wiki/Release/#General_policy

> As port maintainer do I have discretion to decide whether this patch
> can be backported to the release branches or do I need consensus that
> backporting it is ok?

In my interpretation, consensus is still important, but your input is
also very important.
With that said I believe both patches fall into the following:

    ... any patch on master that doesn't change ABI or API is immediately
    suitable for backporting to a stable branch.

This is what I'd do, assuming there are no time constraints:

1. Submit both patches to libc-stable.
2. If nobody objects, push the changes to the stable branch.

-- 
Tulio Magno