From: "Chanho Park" <chanho61.park@samsung.com>
To: "'Krzysztof Kozlowski'" <krzysztof.kozlowski@canonical.com>,
"'Kishon Vijay Abraham I'" <kishon@ti.com>,
"'Vinod Koul'" <vkoul@kernel.org>
Cc: "'Marek Szyprowski'" <m.szyprowski@samsung.com>,
"'Jaehoon Chung'" <jh80.chung@samsung.com>,
"'Alim Akhtar'" <alim.akhtar@samsung.com>,
<linux-phy@lists.infradead.org>
Subject: RE: [PATCH v3 2/2] phy: samsung-ufs: support exynosauto ufs phy driver
Date: Wed, 7 Jul 2021 09:50:21 +0900 [thread overview]
Message-ID: <000001d772ca$10aa8590$31ff90b0$@samsung.com> (raw)
In-Reply-To: <c8327d67-6a73-d06d-271e-62556f9f2fa1@canonical.com>
> > +#include <linux/io.h>
> > +#include <linux/phy/phy.h>
>
> I commented before that io.h is not needed but also phy.h looks unused
> here. If there are used in phy-samsung-ufs.h, they should be put there.
<linux/io.h> will not be necessary and I'll move phy.h inclusion to phy-samsung-ufs.h
Best Regards,
Chanho Park
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2021-07-07 0:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210706021802epcas2p4f1e71284dbe217ebff6887c2879fb489@epcas2p4.samsung.com>
2021-07-06 2:18 ` [PATCH v3 0/2] Support exynosautov9 ufs phy driver Chanho Park
[not found] ` <CGME20210706021804epcas2p1d99074348847a8afe173bdcf80eeac76@epcas2p1.samsung.com>
2021-07-06 2:18 ` [PATCH v3 1/2] phy: samsung-ufs: move phy-exynos7-ufs header Chanho Park
2021-07-06 7:18 ` Krzysztof Kozlowski
[not found] ` <CGME20210706021805epcas2p41840eeb633ef30a5f0812862cb4df174@epcas2p4.samsung.com>
2021-07-06 2:18 ` [PATCH v3 2/2] phy: samsung-ufs: support exynosauto ufs phy driver Chanho Park
2021-07-06 7:20 ` Krzysztof Kozlowski
2021-07-07 0:50 ` Chanho Park [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='000001d772ca$10aa8590$31ff90b0$@samsung.com' \
--to=chanho61.park@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=jh80.chung@samsung.com \
--cc=kishon@ti.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-phy@lists.infradead.org \
--cc=m.szyprowski@samsung.com \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).