From: Vinod Koul <vkoul@kernel.org>
To: Chun-Kuang Hu <chunkuang.hu@kernel.org>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Matthias Brugger <matthias.bgg@gmail.com>,
Chunfeng Yun <chunfeng.yun@mediatek.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org
Subject: Re: [RESEND PATCH 2/3] phy: mediatek: Move mtk_mipi_dsi_phy driver into drivers/phy/mediatek folder
Date: Mon, 30 Nov 2020 16:04:11 +0530 [thread overview]
Message-ID: <20201130103411.GN8403@vkoul-mobl> (raw)
In-Reply-To: <20201116231407.94-3-chunkuang.hu@kernel.org>
On 17-11-20, 07:14, Chun-Kuang Hu wrote:
> mtk_mipi_dsi_phy is currently placed inside mediatek drm driver, but it's
> more suitable to place a phy driver into phy driver folder, so move
> mtk_mipi_dsi_phy driver into phy driver folder.
Acked-By: Vinod Koul <vkoul@kernel.org>
I am thinking this would go thru drm-tree, if not let me know I would
apply this
--
~Vinod
next prev parent reply other threads:[~2020-11-30 10:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 23:14 [RESEND PATCH 0/3] Move Mediatek MIPI DSI PHY driver from DRM folder to PHY folder Chun-Kuang Hu
2020-11-16 23:14 ` [RESEND PATCH 1/3] drm/mediatek: Separate mtk_mipi_tx to an independent module Chun-Kuang Hu
2020-11-16 23:14 ` [RESEND PATCH 2/3] phy: mediatek: Move mtk_mipi_dsi_phy driver into drivers/phy/mediatek folder Chun-Kuang Hu
2020-11-17 3:35 ` Chunfeng Yun
2020-11-17 14:04 ` Chun-Kuang Hu
2020-11-30 10:34 ` Vinod Koul [this message]
2020-12-01 14:30 ` Chun-Kuang Hu
2020-11-16 23:14 ` [RESEND PATCH 3/3] MAINTAINERS: add files for Mediatek DRM drivers Chun-Kuang Hu
2020-11-17 14:05 ` Chun-Kuang Hu
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=20201130103411.GN8403@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=airlied@linux.ie \
--cc=chunfeng.yun@mediatek.com \
--cc=chunkuang.hu@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
/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