From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Vinod Koul <vkoul@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linuxarm@huawei.com, mauro.chehab@huawei.com,
John Stultz <john.stultz@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Kishon Vijay Abraham I <kishon@ti.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh+dt@kernel.org>, Rob Herring <robh@kernel.org>,
Yu Chen <chenyu56@huawei.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/8] Add PHY USB3 drivers for Hikey 970
Date: Fri, 11 Sep 2020 14:04:30 +0200 [thread overview]
Message-ID: <20200911140430.5281b1c3@coco.lan> (raw)
In-Reply-To: <20200911114711.GX77521@vkoul-mobl>
Em Fri, 11 Sep 2020 17:17:11 +0530
Vinod Koul <vkoul@kernel.org> escreveu:
> On 10-09-20, 07:52, Mauro Carvalho Chehab wrote:
> > This patch series add the PHY layer needed in order to support the USB
> > functionality on Hikey 970 boards.
> >
> > v3:
> > - split a namespace patch on two (one with code changes and another
> > one with dt-bindings changes);
> > - placed just the PHY driver on this series. Another series will add the
> > USB HUB driver and the DTS changes required to enable USB support
> > for this board.
>
> I have only cover in my inbox, no other patches. Even lore doesn't show
> the series, not sure what happened here
Gah, it sounds that my scripts did something really weird there.
I changed it while sending some docs patches, as, by adding
all maintainers and MLs for each patch on that series to the
cover letter would produce around ~100 e-mail addresses,
which would hardly be accepted by most of the email servers.
It sounds that I ended breaking it :-(
I'll re-send this patch series.
Thanks,
Mauro
prev parent reply other threads:[~2020-09-11 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 5:52 [PATCH v3 0/8] Add PHY USB3 drivers for Hikey 970 Mauro Carvalho Chehab
2020-09-11 11:47 ` Vinod Koul
2020-09-11 12:04 ` Mauro Carvalho Chehab [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=20200911140430.5281b1c3@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=chenyu56@huawei.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=kishon@ti.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mani@kernel.org \
--cc=mauro.chehab@huawei.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--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 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.