From: Greg K-H <greg@kroah.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Nathan Chancellor <nathan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Char/Misc driver fixes 5.19-rc3
Date: Sun, 19 Jun 2022 13:32:52 +0200 [thread overview]
Message-ID: <Yq8JZMQiUqdmfqx+@kroah.com> (raw)
In-Reply-To: <CE205655-557F-486C-AF6A-099749208327@kroah.com>
On Fri, Jun 17, 2022 at 07:43:26PM +0200, Greg K-H wrote:
>
>
> On June 17, 2022 6:59:50 PM GMT+02:00, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> >On Fri, Jun 17, 2022 at 9:50 AM Nathan Chancellor <nathan@kernel.org> wrote:
> >>
> >> I think you tagged the wrong branch (char-misc-next vs. char-misc-linus)?
> >> The commits below do not match the tag description above.
> >
> >Good catch. I verified the diffstat etc, but yeah, the actual
> >explanation in the tag doesn't match the contents.
> >
> >It's pulled now, and the code changes look fairly harmless, but I
> >suspect Greg will want to send a real pull for the changes that were
> >intended to come in here..
> >
> > Linus
>
>
> Crap, i messed that up. I'm away from my laptop until Monday so I'll
> verify it then. The one time i go out of town for the weekend...
Heat drove us home a day early so I've now created a new tag, on the
correct branch and sent the pull request. Sorry about the mess, all
should be good now.
greg k-h
prev parent reply other threads:[~2022-06-19 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 8:15 Greg KH
2022-06-17 15:00 ` pr-tracker-bot
2022-06-17 16:50 ` Nathan Chancellor
2022-06-17 16:59 ` Linus Torvalds
2022-06-17 17:43 ` Greg K-H
2022-06-19 11:32 ` Greg K-H [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=Yq8JZMQiUqdmfqx+@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®