From: Amelie DELAUNAY <amelie.delaunay@st.com>
To: Felipe Balbi <balbi@kernel.org>,
Minas Harutyunyan <hminas@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
Fabrice GASNIER <fabrice.gasnier@st.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: Re: [PATCH v3 0/3] Add USB role switch support to DWC2
Date: Mon, 27 Jul 2020 11:37:22 +0200 [thread overview]
Message-ID: <94748764-43b2-f11e-fd12-20ef3970c09a@st.com> (raw)
In-Reply-To: <871rl0q46a.fsf@kernel.org>
Hi,
On 7/24/20 6:16 PM, Felipe Balbi wrote:
> Amelie DELAUNAY <amelie.delaunay@st.com> writes:
>
>> Hi,
>>
>> On 7/24/20 3:50 PM, Felipe Balbi wrote:
>>>
>>> (no top-posting, please)
>>>
>>> Hi,
>>>
>>> Amelie DELAUNAY <amelie.delaunay@st.com> writes:
>>>> Series dropped.
>>>
>>> what do you mean with this? Should I drop all patches related with this series?
>>>
>>
>> As v1 patches were in your next branch, I've prepared a new patchset
>> which contains fixes, on top of you next branch :
>> https://lore.kernel.org/patchwork/project/lkml/list/?series=454959
>>
>>
>> What do you prefer ? Drop all patches related to the v1 "Add USB role
>> switch support to DWC2" series and I send a v4 in replacement or keep
>> all patches and wait for new series review ?
>
> I've dropped those because they caused the build breakage :-) I can take
> a new series, let's take the opportunity to avoid the build regression.
>
Sure! I've sent the v4, rebased on your testing/next because your next
still contains the v1 patches, with the fix for build issue, and
adressing Martin's comments. I drop the fixes series.
Regards,
Amelie
prev parent reply other threads:[~2020-07-27 9:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 10:47 [PATCH v3 0/3] Add USB role switch support to DWC2 Amelie Delaunay
2020-07-24 10:47 ` [PATCH v3 1/3] usb: dwc2: override PHY input signals with usb role switch support Amelie Delaunay
2020-07-24 10:47 ` [PATCH v3 2/3] dt-bindings: usb: dwc2: add optional usb-role-switch property Amelie Delaunay
2020-07-24 10:47 ` [PATCH v3 3/3] usb: dwc2: don't use ID/Vbus detection if usb-role-switch on STM32MP15 SoCs Amelie Delaunay
2020-07-24 12:43 ` [PATCH v3 0/3] Add USB role switch support to DWC2 Amelie DELAUNAY
2020-07-24 13:50 ` Felipe Balbi
2020-07-24 13:58 ` Amelie DELAUNAY
2020-07-24 16:16 ` Felipe Balbi
2020-07-27 9:37 ` Amelie DELAUNAY [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=94748764-43b2-f11e-fd12-20ef3970c09a@st.com \
--to=amelie.delaunay@st.com \
--cc=alexandre.torgue@st.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=gregkh@linuxfoundation.org \
--cc=hminas@synopsys.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-usb@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mcoquelin.stm32@gmail.com \
--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).