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 09:51:44 +0100 [thread overview]
Message-ID: <20190118085144.GA9572@kroah.com> (raw)
In-Reply-To: <20190114201608.17514-1-lkundrak@v3.sk>
On Mon, Jan 14, 2019 at 09:16:08PM +0100, Lubomir Rintel wrote:
> This fixes autoloading the module by the OF compatible string.
>
> Fixes: 813e18b18a87f31c5b216ea7546127deac3ae1ae
In the future, this type of line should be written as:
Fixes: 813e18b18a87 ("USB: EHCI: ehci-mv: add DT support")
I'll change this in the patch, but next time be more careful.
thanks,
greg k-h
next prev parent reply other threads:[~2019-01-18 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 20:16 [PATCH] USB: EHCI: ehci-mv: add MODULE_DEVICE_TABLE Lubomir Rintel
2019-01-18 8:51 ` Greg Kroah-Hartman [this message]
2019-01-18 8:52 ` Greg Kroah-Hartman
2019-01-18 8:56 ` Lubomir Rintel
2019-01-18 9:05 ` Greg Kroah-Hartman
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=20190118085144.GA9572@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox