linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [GIT PULL] pin control fixes for the v6.1 series
Date: Fri, 21 Oct 2022 10:34:46 -0700	[thread overview]
Message-ID: <CAHk-=win6D4mgA04-D+S96n4aTNU-hx94e2ftF7rQjHb46O0Kw@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdbqRy5pXiy2r5CBiBXd8j7VbXKq40pmx_eXtFMynyAMug@mail.gmail.com>

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

      parent reply	other threads:[~2022-10-21 17:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

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='CAHk-=win6D4mgA04-D+S96n4aTNU-hx94e2ftF7rQjHb46O0Kw@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).