From: Peter Chen <peter.chen@nxp.com>
To: Pawel Laszczak <pawell@cadence.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"balbi@kernel.org" <balbi@kernel.org>,
"colin.king@canonical.com" <colin.king@canonical.com>,
"rogerq@ti.com" <rogerq@ti.com>,
"kurahul@cadence.com" <kurahul@cadence.com>,
"nsekhar@ti.com" <nsekhar@ti.com>
Subject: Re: [PATCH v3 10/10] MAINTAINERS: add Cadence USBSSP DRD IP driver entry
Date: Wed, 25 Nov 2020 01:10:20 +0000 [thread overview]
Message-ID: <20201125010951.GC9929@b29397-desktop> (raw)
In-Reply-To: <20201119141307.8342-11-pawell@cadence.com>
On 20-11-19 15:13:07, Pawel Laszczak wrote:
> Patch adds entry for USBSSP (CDNSP) driver into MAINTARNERS file.
>
> Signed-off-by: Pawel Laszczak <pawell@cadence.com>
> ---
> MAINTAINERS | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 842fef329119..70c31fd2cd61 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -3867,6 +3867,14 @@ S: Maintained
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb.git
> F: Documentation/devicetree/bindings/usb/cdns,usb3.yaml
> F: drivers/usb/cdns3/
> +X: drivers/usb/cdns3/cdnsp*
> +
> +CADENCE USBSSP DRD IP DRIVER
> +M: Pawel Laszczak <pawell@cadence.com>
> +L: linux-usb@vger.kernel.org
> +S: Maintained
> +F: drivers/usb/cdns3/
> +X: drivers/usb/cdns3/cdns3*
>
Hi Pawel,
You may add "T" for which tree for cdns3 ssp driver.
--
Thanks,
Peter Chen
next prev parent reply other threads:[~2020-11-25 1:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 14:12 [PATCH v3 00/10] Introduced new Cadence USBSSP DRD Driver Pawel Laszczak
2020-11-19 14:12 ` [PATCH v3 01/10] usb: cdns3: Add support for DRD CDNSP Pawel Laszczak
2020-11-19 14:12 ` [PATCH v3 02/10] usb: cdns3: Split core.c into cdns3-plat and core.c file Pawel Laszczak
2020-11-19 14:13 ` [PATCH v3 03/10] usb: cdns3: Moves reusable code to separate module Pawel Laszczak
2020-11-19 14:13 ` [PATCH v3 04/10] usb: cdns3: Refactoring names in reusable code Pawel Laszczak
2020-11-19 14:13 ` [PATCH v3 05/10] usb: cdns3: Changed type of gadget_dev in cdns structure Pawel Laszczak
2020-11-19 14:13 ` [PATCH v3 06/10] usb: cdnsp: Device side header file for CDNSP driver Pawel Laszczak
2020-11-19 14:13 ` [PATCH v3 07/10] usb: cdnsp: cdns3 Add main part of Cadence USBSSP DRD Driver Pawel Laszczak
2020-11-19 14:13 ` [PATCH v3 08/10] usb: cdnsp: Add tracepoints for CDNSP driver Pawel Laszczak
2020-11-19 14:13 ` [PATCH v3 09/10] usb: cdns3: Change file names for cdns3 driver Pawel Laszczak
2020-11-19 14:13 ` [PATCH v3 10/10] MAINTAINERS: add Cadence USBSSP DRD IP driver entry Pawel Laszczak
2020-11-25 1:10 ` Peter Chen [this message]
2020-11-25 4:41 ` Pawel Laszczak
2020-11-24 7:50 ` [PATCH v3 00/10] Introduced new Cadence USBSSP DRD Driver Peter Chen
2020-11-24 9:21 ` Pawel Laszczak
2020-11-24 9:35 ` Sekhar Nori
2020-11-24 9:52 ` Pawel Laszczak
2020-11-25 15:03 ` Sekhar Nori
2020-11-25 6:07 ` Pawel Laszczak
2020-11-25 6:53 ` Peter Chen
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=20201125010951.GC9929@b29397-desktop \
--to=peter.chen@nxp.com \
--cc=balbi@kernel.org \
--cc=colin.king@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=kurahul@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=pawell@cadence.com \
--cc=rogerq@ti.com \
/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