From: Vinod Koul <vkoul@kernel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Alex Dewar <alex.dewar90@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Yu Chen <chenyu56@huawei.com>,
devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 5/5] phy: phy-hi3670-usb3: move driver from staging into phy
Date: Thu, 4 Feb 2021 13:18:37 +0530 [thread overview]
Message-ID: <20210204074837.GE3079@vkoul-mobl.Dlink> (raw)
In-Reply-To: <82ce73ac9a383f0cae0faded5ec6fef2d3417d3c.1611052729.git.mchehab+huawei@kernel.org>
On 19-01-21, 11:44, Mauro Carvalho Chehab wrote:
> The phy USB3 driver for Hisilicon 970 (hi3670) is ready
> for mainstream. Mode it from staging into the main driver's
> phy/ directory.
Acked-By: Vinod Koul <vkoul@kernel.org>
I think it makes sense if Greg applies this as well
--
~Vinod
next prev parent reply other threads:[~2021-02-04 7:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 10:44 [PATCH v4 0/5] Promote Hikey 970 USB phy out of staging Mauro Carvalho Chehab
2021-01-19 10:44 ` [PATCH v4 1/5] staging: hikey9xx: phy-hi3670-usb3: use bitfield macros Mauro Carvalho Chehab
2021-01-19 10:44 ` [PATCH v4 2/5] staging: hikey9xx: phy-hi3670-usb3: adjust retry logic Mauro Carvalho Chehab
2021-01-19 10:44 ` [PATCH v4 3/5] staging: hikey9xx: phy-hi3670-usb3: hi3670_is_abbclk_seleted() returns bool Mauro Carvalho Chehab
2021-01-19 10:44 ` [PATCH v4 4/5] staging: hikey9xx: phy-hi3670-usb3.yaml: add a blank line Mauro Carvalho Chehab
2021-01-19 10:44 ` [PATCH v4 5/5] phy: phy-hi3670-usb3: move driver from staging into phy Mauro Carvalho Chehab
2021-02-04 7:48 ` Vinod Koul [this message]
2021-02-05 22:13 ` Rob Herring
2021-01-26 17:49 ` [PATCH v4 0/5] Promote Hikey 970 USB phy out of staging Greg Kroah-Hartman
2021-02-04 7:49 ` Vinod Koul
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=20210204074837.GE3079@vkoul-mobl.Dlink \
--to=vkoul@kernel.org \
--cc=alex.dewar90@gmail.com \
--cc=chenyu56@huawei.com \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®