Re: [GIT PULL] Qualcomm pin control fixes for v7.3-rc4

[Linus Walleij]

On Mon, Sep 21, 2026 at 11:04 AM Bartosz Golaszewski <brgl@xxxxxxxxxx> wrote:
> On Fri, 18 Sep 2026 19:01:35 +0200, Linus Walleij <linusw@xxxxxxxxxx> said:
> > On Thu, Sep 17, 2026 at 11:44 AM Bartosz Golaszewski
> > <bartosz.golaszewski@xxxxxxxxxxxxxxxx> wrote:
> >
> >> Please pull the following set of Qualcomm pin controller fixes for the
> >> next RC.
> >
> > This was not based on -rc1 like my tree so I just pulled off
> > the two commits and signed them off on top of my existing
> > patch stack so I don't have to pull in -rc2.
> >
>
> Ah, I think we never discussed the upstream tag policy. I typically base my
> pull-requests targeting the *current* release (in this case: v7.3) on whatever
> the latest upstream tag is. I try to base my for-next trees on top of the
> current rc1 unless there are conflicting commits already upstream, in which
> case I pull the earliest required upstream tag.
>
> Do you want me to prefer rc1 even for fixes for pinctrl PRs?

The policy is something like the latest that was around when
I was starting to collect fixes.

I simply don't send pull requests for every RC. When I do,
I will then rebase on top of the one which has my previous
pull request so I don't send the same thing more than once.

If there is any policy it is "check what is under the patches
on the pinctrl fixes branch". I don't know anthing better. But
generally -rc1 always works as least common ancestor.

Yours,
Linus Walleij