From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Bin Liu <b-liu@ti.com>, Chen-Yu Tsai <wens@csie.org>,
Samuel Holland <samuel@sholland.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Icenowy Zheng <uwu@icenowy.me>,
devicetree@vger.kernel.org, soc@kernel.org,
linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev
Subject: Re: [PATCH v5 02/11] usb: musb: sunxi: add support for the F1C100s MUSB controller
Date: Wed, 1 Feb 2023 06:06:18 +0100 [thread overview]
Message-ID: <Y9nzSm7ZKYVsHA6m@kroah.com> (raw)
In-Reply-To: <20230131225253.04369efc@slackpad.lan>
On Tue, Jan 31, 2023 at 10:52:53PM +0000, Andre Przywara wrote:
> On Wed, 11 Jan 2023 01:53:23 +0000
> Andre Przywara <andre.przywara@arm.com> wrote:
>
> Hi Bin, Greg,
>
> > From: Icenowy Zheng <uwu@icenowy.me>
> >
> > The suniv SoC has a MUSB controller like the one in A33, but with a SRAM
> > region to be claimed.
> >
> > Add support for it.
>
> is there any chance you could take this patch (and the next one,
> ideally) through your tree? And not sure if the binding patch (01/11)
> should also go this way?
Please resend just the patches you want me to apply, picking them out of
an old series is very difficult to do.
thanks,
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-01 5:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 1:53 [PATCH v5 00/11] ARM: suniv: USB and two new boards support Andre Przywara
2023-01-11 1:53 ` [PATCH v5 01/11] dt-bindings: usb: sunxi-musb: add F1C100s MUSB compatible string Andre Przywara
2023-01-11 1:53 ` [PATCH v5 02/11] usb: musb: sunxi: add support for the F1C100s MUSB controller Andre Przywara
2023-01-31 22:52 ` Andre Przywara
2023-02-01 5:06 ` Greg Kroah-Hartman [this message]
2023-01-11 1:53 ` [PATCH v5 03/11] usb: musb: sunxi: Introduce config struct Andre Przywara
2023-01-27 20:22 ` Jernej Škrabec
2023-01-11 1:53 ` [PATCH v5 04/11] ARM: dts: suniv: add USB-related device nodes Andre Przywara
2023-01-11 1:53 ` [PATCH v5 05/11] ARM: dts: suniv: licheepi-nano: enable USB Andre Przywara
2023-01-11 1:53 ` [PATCH v5 06/11] dt-bindings: vendor-prefixes: add Source Parts Andre Przywara
2023-01-11 1:53 ` [PATCH v5 07/11] dt-binding: arm: sunxi: add compatible strings for PopStick v1.1 Andre Przywara
2023-01-11 1:53 ` [PATCH v5 08/11] ARM: dts: suniv: add device tree " Andre Przywara
2023-01-11 1:53 ` [PATCH v5 09/11] dt-bindings: vendor-prefixes: add Lctech name Andre Przywara
2023-01-11 1:53 ` [PATCH v5 10/11] dt-bindings: arm: sunxi: add compatible strings for Lctech Pi Andre Przywara
2023-01-11 1:53 ` [PATCH v5 11/11] ARM: dts: suniv: Add Lctech Pi F1C200s devicetree Andre Przywara
2023-01-18 12:11 ` [PATCH v5 00/11] ARM: suniv: USB and two new boards support Andre Przywara
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=Y9nzSm7ZKYVsHA6m@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andre.przywara@arm.com \
--cc=b-liu@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=soc@kernel.org \
--cc=uwu@icenowy.me \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).