From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Pawel Laszczak <pawell@cadence.com>,
balbi@kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 5.4 05/12] usb: cdns2: Device side header file for CDNS2 driver
Date: Mon, 24 Jul 2023 06:08:13 +0200 [thread overview]
Message-ID: <2023072451-candied-imbecile-d4a9@gregkh> (raw)
In-Reply-To: <20230724013426.2333833-5-sashal@kernel.org>
On Sun, Jul 23, 2023 at 09:34:18PM -0400, Sasha Levin wrote:
> From: Pawel Laszczak <pawell@cadence.com>
>
> [ Upstream commit 0ca2026eea104adc1d0d356bca35915a1ab6e3e9 ]
>
> Patch defines macros, registers and structures used by
> Device side driver.
>
> Signed-off-by: Pawel Laszczak <pawell@cadence.com>
> Message-ID: <20230602102644.77470-2-pawell@cadence.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
> drivers/usb/gadget/udc/cdns2/cdns2-gadget.h | 707 ++++++++++++++++++++
> 1 file changed, 707 insertions(+)
> create mode 100644 drivers/usb/gadget/udc/cdns2/cdns2-gadget.h
This just adds a .h file for a new driver that isn't being backported,
so no need to include it into any stable release.
thanks,
greg k-h
prev parent reply other threads:[~2023-07-24 4:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230724013426.2333833-1-sashal@kernel.org>
2023-07-24 1:34 ` [PATCH AUTOSEL 5.4 03/12] xhci: Don't require a valid get_quirks() function pointer during xhci setup Sasha Levin
2023-07-24 1:34 ` [PATCH AUTOSEL 5.4 04/12] usb: chipidea: imx: don't request QoS for imx8ulp Sasha Levin
2023-07-24 1:34 ` [PATCH AUTOSEL 5.4 05/12] usb: cdns2: Device side header file for CDNS2 driver Sasha Levin
2023-07-24 4:08 ` Greg Kroah-Hartman [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=2023072451-candied-imbecile-d4a9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pawell@cadence.com \
--cc=sashal@kernel.org \
--cc=stable@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