From: Greg KH <gregkh@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Saravana Kannan <saravanak@google.com>
Subject: Re: [GIT PULL] Driver core updates for 6.3-rc1
Date: Fri, 24 Feb 2023 14:53:39 +0100 [thread overview]
Message-ID: <Y/jBY9PJl68Lnva9@kroah.com> (raw)
In-Reply-To: <CAMuHMdXT-LqqfzLqUHpORbNz89F4eGJrJY2TJdoM5+MME_4fdw@mail.gmail.com>
On Fri, Feb 24, 2023 at 02:48:55PM +0100, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Fri, Feb 24, 2023 at 2:01 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> > The following changes since commit 2241ab53cbb5cdb08a6b2d4688feb13971058f65:
> >
> > Linux 6.2-rc5 (2023-01-21 16:27:01 -0800)
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git tags/driver-core-6.3-rc1
> >
> > for you to fetch changes up to 88cd618dcc7b63baa1478730b02eaba3e3148467:
> >
> > debugfs: drop inline constant formatting for ERR_PTR(-ERROR) (2023-02-20 14:14:56 +0100)
> >
> > ----------------------------------------------------------------
> > Driver core changes for 6.3-rc1
>
> Thanks for your PR!
>
> > All of these have been in linux-next for a while with no reported
> > problems.
>
> I think you should drop this sentence from your boilerplate, to avoid
> confusion among people who reported regressions and/or posted
> fixes that you promised to queue up after your PR is sent to Linus.
Ah, yeah, I had forgotten about your bug report / fix when writing this.
I'll send that to Linus after this is pulled, my fault.
thanks,
greg k-h
next prev parent reply other threads:[~2023-02-24 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 12:52 [GIT PULL] Driver core updates for 6.3-rc1 Greg KH
2023-02-24 13:48 ` Geert Uytterhoeven
2023-02-24 13:53 ` Greg KH [this message]
2023-02-24 21:16 ` pr-tracker-bot
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=Y/jBY9PJl68Lnva9@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saravanak@google.com \
--cc=sfr@canb.auug.org.au \
--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