From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: linuxarm@huawei.com, mauro.chehab@huawei.com,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH v15 0/3] Move HiSilicon 6421v600 SPMI and USB drivers out of staging
Date: Fri, 23 Jul 2021 10:14:44 +0200 [thread overview]
Message-ID: <YPp6dNuhPiLdgVKf@kroah.com> (raw)
In-Reply-To: <cover.1627025657.git.mchehab+huawei@kernel.org>
On Fri, Jul 23, 2021 at 09:40:05AM +0200, Mauro Carvalho Chehab wrote:
> Hi Greg,
>
> Those are the remaining patches needed for USB3 to start working on HiKey 970.
>
> I would prefer to have those merged during this cycle, as the PCIe patchset
> currently under review depends on patch 1 and 2 of this series.
>
> So, I dropped the cleanup patch from this series, due to a merge conflict with
> the regulator's tree. I'll re-submit it against the mfd tree after the merge window.
>
> Mauro Carvalho Chehab (3):
> mfd: hi6421-spmi-pmic: move driver from staging
> dts: hisilicon: add support for the PMIC found on Hikey 970
> dts: hisilicon: add support for USB3 on Hikey 970
I've applied patch 1 here.
The other two I need acks from the DT maintainers before I can do
anything with them.
thanks,
greg k-h
next prev parent reply other threads:[~2021-07-23 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 7:40 [PATCH v15 0/3] Move HiSilicon 6421v600 SPMI and USB drivers out of staging Mauro Carvalho Chehab
2021-07-23 7:40 ` [PATCH v15 1/3] mfd: hi6421-spmi-pmic: move driver from staging Mauro Carvalho Chehab
2021-07-23 22:30 ` Rob Herring
2021-07-23 8:14 ` Greg Kroah-Hartman [this message]
2021-07-23 22:32 ` [PATCH v15 0/3] Move HiSilicon 6421v600 SPMI and USB drivers out of staging Rob Herring
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=YPp6dNuhPiLdgVKf@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linuxarm@huawei.com \
--cc=mauro.chehab@huawei.com \
--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;
as well as URLs for NNTP newsgroup(s).