From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: USB: EHCI: ehci-mv: add MODULE_DEVICE_TABLE
Date: Fri, 18 Jan 2019 10:05:59 +0100 [thread overview]
Message-ID: <20190118090559.GA11182@kroah.com> (raw)
On Fri, Jan 18, 2019 at 09:56:53AM +0100, Lubomir Rintel wrote:
> On Fri, 2019-01-18 at 09:52 +0100, Greg Kroah-Hartman wrote:
> > On Mon, Jan 14, 2019 at 09:16:08PM +0100, Lubomir Rintel wrote:
> > > This fixes autoloading the module by the OF compatible string.
> > >
> > > Fixes: 813e18b18a87 ("USB: EHCI: ehci-mv: add DT support")
> > > Cc: stable@vger.kernel.org # v4.19+
> >
> > Wait, why 4.19? 813e18b18a87 is in 4.20, not 4.19, so why would this
> > matter to 4.19 at all?
>
> You're right.
>
> Sorry. (I've naively used "git describe 813e18b18a87" to guess the
> release this went to, failing to realize that the commit went to main
> tree via merge. I guess I should've done a git tag --contains instead.)
Thanks for verifying, I'll fix that up too.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] USB: EHCI: ehci-mv: add MODULE_DEVICE_TABLE
Date: Fri, 18 Jan 2019 10:05:59 +0100 [thread overview]
Message-ID: <20190118090559.GA11182@kroah.com> (raw)
In-Reply-To: <6f756e0e84275266848dab28866a9250bc43088b.camel@v3.sk>
On Fri, Jan 18, 2019 at 09:56:53AM +0100, Lubomir Rintel wrote:
> On Fri, 2019-01-18 at 09:52 +0100, Greg Kroah-Hartman wrote:
> > On Mon, Jan 14, 2019 at 09:16:08PM +0100, Lubomir Rintel wrote:
> > > This fixes autoloading the module by the OF compatible string.
> > >
> > > Fixes: 813e18b18a87 ("USB: EHCI: ehci-mv: add DT support")
> > > Cc: stable@vger.kernel.org # v4.19+
> >
> > Wait, why 4.19? 813e18b18a87 is in 4.20, not 4.19, so why would this
> > matter to 4.19 at all?
>
> You're right.
>
> Sorry. (I've naively used "git describe 813e18b18a87" to guess the
> release this went to, failing to realize that the commit went to main
> tree via merge. I guess I should've done a git tag --contains instead.)
Thanks for verifying, I'll fix that up too.
thanks,
greg k-h
next reply other threads:[~2019-01-18 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 9:05 Greg Kroah-Hartman [this message]
2019-01-18 9:05 ` [PATCH] USB: EHCI: ehci-mv: add MODULE_DEVICE_TABLE Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2019-01-18 8:56 Lubomir Rintel
2019-01-18 8:56 ` [PATCH] " Lubomir Rintel
2019-01-18 8:52 Greg Kroah-Hartman
2019-01-18 8:52 ` [PATCH] " Greg Kroah-Hartman
2019-01-18 8:51 Greg Kroah-Hartman
2019-01-18 8:51 ` [PATCH] " Greg Kroah-Hartman
2019-01-14 20:16 Lubomir Rintel
2019-01-14 20:16 ` [PATCH] " Lubomir Rintel
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=20190118090559.GA11182@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.