From: Felipe Balbi <balbi@kernel.org>
To: "周琰杰 (Zhou Yanjie)" <zhouyanjie@wanyeetech.com>,
gregkh@linuxfoundation.org, robh+dt@kernel.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, paul@crapouillou.net,
prasannatsmkumar@gmail.com, dongsheng.qiu@ingenic.com,
aric.pzqi@ingenic.com, rick.tyliu@ingenic.com,
yanfei.li@ingenic.com, sernia.zhou@foxmail.com,
zhenwenjin@gmail.com
Subject: Re: [PATCH v5 0/4] Add USB PHY support for new Ingenic SoCs.
Date: Thu, 23 Jul 2020 12:19:35 +0300 [thread overview]
Message-ID: <87tuxyoafs.fsf@kernel.org> (raw)
In-Reply-To: <20200723061301.82583-1-zhouyanjie@wanyeetech.com>
[-- Attachment #1: Type: text/plain, Size: 402 bytes --]
周琰杰 (Zhou Yanjie) <zhouyanjie@wanyeetech.com> writes:
> 1.separate the adjustments to the code style into
> a separate patch.
> 2.Modify the help message, make it more future-proof.
> 3.Drop the unnecessary comment about hardware reset.
> 4.Create 'soc_info' structures instead having ID_* as platform data.
For v5.10, make sure to move your phy driver to drivers/phy.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-07-23 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 6:12 [PATCH v5 0/4] Add USB PHY support for new Ingenic SoCs 周琰杰 (Zhou Yanjie)
2020-07-23 6:12 ` [PATCH v5 1/4] dt-bindings: USB: Add bindings " 周琰杰 (Zhou Yanjie)
2020-07-23 6:12 ` [PATCH v5 2/4] USB: PHY: JZ4770: Unify code style and simplify code 周琰杰 (Zhou Yanjie)
2020-07-23 6:13 ` [PATCH v5 3/4] USB: PHY: JZ4770: Add support for new Ingenic SoCs 周琰杰 (Zhou Yanjie)
2020-07-24 2:36 ` kernel test robot
2020-07-23 6:13 ` [PATCH v5 4/4] USB: PHY: JZ4770: Reformat the code to align it 周琰杰 (Zhou Yanjie)
2020-07-23 9:19 ` Felipe Balbi [this message]
2020-07-25 3:12 ` [PATCH v5 0/4] Add USB PHY support for new Ingenic SoCs Zhou Yanjie
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=87tuxyoafs.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=aric.pzqi@ingenic.com \
--cc=devicetree@vger.kernel.org \
--cc=dongsheng.qiu@ingenic.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=prasannatsmkumar@gmail.com \
--cc=rick.tyliu@ingenic.com \
--cc=robh+dt@kernel.org \
--cc=sernia.zhou@foxmail.com \
--cc=yanfei.li@ingenic.com \
--cc=zhenwenjin@gmail.com \
--cc=zhouyanjie@wanyeetech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.