linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [GIT PULL] pin control fixes for the v6.1 series
@ 2022-10-21  8:55 Linus Walleij
  2022-10-21  9:00 ` pr-tracker-bot
  2022-10-21 17:34 ` Linus Torvalds
  0 siblings, 2 replies; 3+ messages in thread
From: Linus Walleij @ 2022-10-21  8:55 UTC (permalink / raw)
  To: Linus Torvalds; +Cc: linux-kernel, open list:GPIO SUBSYSTEM

Hi Linus,

here are some first pin control fixes for the v6.1 series.
I try to be quicker to get fixes upstream now.

Details in the signed tag!

Please pull it in.

Yours,
Linus Walleij

The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:

  Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-v6.1-2

for you to fetch changes up to 9abf2313adc1ca1b6180c508c25f22f9395cc780:

  Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)

----------------------------------------------------------------
Some pin control fixes for v6.1:

- Fix typos in UART1 and MMC in the Ingenic driver.

- A really well researched glitch bug fix to the Qualcomm driver
  that was tracked down and fixed by Dough Anderson from
  Chromium. Hats off for this one!

- Revert two patches on the Xilinx ZynqMP driver: this needs a
  proper solution making use of firmware version information to
  adapt to different firmware releases.

- Fix interrupt triggers in the Ocelot driver.

----------------------------------------------------------------

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [GIT PULL] pin control fixes for the v6.1 series
  2022-10-21  8:55 [GIT PULL] pin control fixes for the v6.1 series Linus Walleij
@ 2022-10-21  9:00 ` pr-tracker-bot
  2022-10-21 17:34 ` Linus Torvalds
  1 sibling, 0 replies; 3+ messages in thread
From: pr-tracker-bot @ 2022-10-21  9:00 UTC (permalink / raw)
  To: Linus Walleij; +Cc: Linus Torvalds, linux-kernel, open list:GPIO SUBSYSTEM

The pull request you sent on Fri, 21 Oct 2022 10:55:52 +0200:

> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git tags/pinctrl-v6.1-2

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/664609e49f1c84fc97987b2bf64544e586b8849c

Thank you!

-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [GIT PULL] pin control fixes for the v6.1 series
  2022-10-21  8:55 [GIT PULL] pin control fixes for the v6.1 series Linus Walleij
  2022-10-21  9:00 ` pr-tracker-bot
@ 2022-10-21 17:34 ` Linus Torvalds
  1 sibling, 0 replies; 3+ messages in thread
From: Linus Torvalds @ 2022-10-21 17:34 UTC (permalink / raw)
  To: Linus Walleij; +Cc: linux-kernel, open list:GPIO SUBSYSTEM

On Fri, Oct 21, 2022 at 1:56 AM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> for you to fetch changes up to 9abf2313adc1ca1b6180c508c25f22f9395cc780:
>
>   Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)

Well, I have *no* idea what you did here, but the pull request claims
that I should fetch that Linux 6.1-rc1 commit, which I obviously
already have in my tree.

That's also why the pull request then doesn't have any diffstat
(because there's no diff), and why pr-tracket-bot immediately replied
with "it's already been merged".

And indeed, when I fetch that 'pinctrl-v6.1-2' tag, it does have your
signed tag, but it just points to my -rc1 commit.

In other words - can you please try that pull request again after
re-tagging properly - because it's all kinds of messed up right now.

                Linus

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-10-21 17:35 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-10-21  8:55 [GIT PULL] pin control fixes for the v6.1 series Linus Walleij
2022-10-21  9:00 ` pr-tracker-bot
2022-10-21 17:34 ` Linus Torvalds

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).