From: "Nobuhiro Iwamatsu" <nobuhiro1.iwamatsu@toshiba.co.jp>
To: <pavel@denx.de>, <prabhakar.mahadev-lad.rj@bp.renesas.com>
Cc: <cip-dev@lists.cip-project.org>, <biju.das.jz@bp.renesas.com>
Subject: Re: [cip-dev] [PATCH 4.19.y-cip 0/6] Renesas RZ/G2H add USB{2,3} support
Date: Fri, 6 Nov 2020 07:09:33 +0000 [thread overview]
Message-ID: <OSBPR01MB2983B5BB3FC2BBF6AD90C97392ED0@OSBPR01MB2983.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20201105121203.GA11467@duo.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
Hi,
> -----Original Message-----
> From: Pavel Machek [mailto:pavel@denx.de]
> Sent: Thursday, November 5, 2020 9:12 PM
> To: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> Cc: cip-dev@lists.cip-project.org; iwamatsu nobuhiro(岩松 信洋 □ＳＷＣ◯ＡＣＴ)
> <nobuhiro1.iwamatsu@toshiba.co.jp>; Pavel Machek <pavel@denx.de>; Biju Das <biju.das.jz@bp.renesas.com>
> Subject: Re: [PATCH 4.19.y-cip 0/6] Renesas RZ/G2H add USB{2,3} support
>
> Hi!
>
> > This patch series adds USB{2,3} support to Renesas RZ/G2H SoC.
> >
> > All the patches have been cherry-picked from Linux v5.10-rc2.
>
> Series looks ok to me and passes our testing, I can apply it if there
> are no other comments.
Looks good to me too. I applied and pushed to kernel.org.
Best regards,
Nobuhiro
[-- Attachment #2: Type: text/plain, Size: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5753): https://lists.cip-project.org/g/cip-dev/message/5753
Mute This Topic: https://lists.cip-project.org/mt/78047670/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2020-11-06 7:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 9:50 [cip-dev] [PATCH 4.19.y-cip 0/6] Renesas RZ/G2H add USB{2,3} support Lad Prabhakar
2020-11-05 9:50 ` [cip-dev] [PATCH 4.19.y-cip 1/6] dt-bindings: phy: renesas,usb2-phy: Add r8a774e1 support Lad Prabhakar
2020-11-05 9:50 ` [cip-dev] [PATCH 4.19.y-cip 2/6] dt-bindings: phy: renesas,usb3-phy: " Lad Prabhakar
2020-11-05 9:50 ` [cip-dev] [PATCH 4.19.y-cip 3/6] dt-bindings: dma: renesas,usb-dmac: Add binding for r8a774e1 Lad Prabhakar
2020-11-05 9:50 ` [cip-dev] [PATCH 4.19.y-cip 4/6] arm64: dts: renesas: r8a774e1: Add USB2.0 phy and host (EHCI/OHCI) device nodes Lad Prabhakar
2020-11-05 11:28 ` Pavel Machek
2020-11-05 11:50 ` Lad Prabhakar
2020-12-01 9:48 ` Pavel Machek
2020-11-05 9:50 ` [cip-dev] [PATCH 4.19.y-cip 5/6] arm64: dts: renesas: r8a774e1: Add USB3.0 " Lad Prabhakar
2020-11-05 9:50 ` [cip-dev] [PATCH 4.19.y-cip 6/6] arm64: dts: renesas: r8a774e1: Add USB-DMAC and HSUSB " Lad Prabhakar
2020-11-05 12:12 ` [cip-dev] [PATCH 4.19.y-cip 0/6] Renesas RZ/G2H add USB{2,3} support Pavel Machek
2020-11-06 7:09 ` Nobuhiro Iwamatsu [this message]
2020-11-06 9:16 ` Lad Prabhakar
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=OSBPR01MB2983B5BB3FC2BBF6AD90C97392ED0@OSBPR01MB2983.jpnprd01.prod.outlook.com \
--to=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=biju.das.jz@bp.renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=pavel@denx.de \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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;
as well as URLs for NNTP newsgroup(s).