From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Alexandre Torgue <alexandre.torgue@st.com>,
Amelie DELAUNAY <amelie.delaunay@st.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
John Youn <johnyoun@synopsys.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>,
Benjamin GAIGNARD <benjamin.gaignard@st.com>
Subject: Re: [PATCHv2 0/7] Add support for USB OTG on STM32F7
Date: Thu, 12 Oct 2017 14:53:26 +0300 [thread overview]
Message-ID: <8760bk1t1l.fsf@linux.intel.com> (raw)
In-Reply-To: <878tgg1t5a.fsf@linux.intel.com>
Hi,
Felipe Balbi <felipe.balbi@linux.intel.com> writes:
>>>> I thought that patches 1 and 2, as they are "driver" patches, had to be
>>>> applied on USB tree (so Felipe's one), and the others (3 to 7) had to be
>>>> applied on STM32-DT tree (Alex's one). Did I miss something?
>>>
>>> patch 1 is documentation, right? Without the documentation patch,
>>> checkpatch will cringe :-) So either way works.
>>>
>>> If you insist, I can take 1-2 through my tree. No worries.
>>
>> I don't want to insist :) but for me it is better (and more safe) if you
>> take patch 1&2 in your tree, and will take others in mine.
>
> Okay, I'll apply 1&2
they are now in my testing/next and next branches.
--
balbi
WARNING: multiple messages have this Message-ID (diff)
From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Alexandre Torgue <alexandre.torgue@st.com>,
Amelie DELAUNAY <amelie.delaunay@st.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
John Youn <johnyoun@synopsys.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>,
Benjamin GAIGNARD <benjamin.gaignard@st.com>
Subject: Re: [PATCHv2 0/7] Add support for USB OTG on STM32F7
Date: Thu, 12 Oct 2017 14:53:26 +0300 [thread overview]
Message-ID: <8760bk1t1l.fsf@linux.intel.com> (raw)
In-Reply-To: <878tgg1t5a.fsf@linux.intel.com>
Hi,
Felipe Balbi <felipe.balbi@linux.intel.com> writes:
>>>> I thought that patches 1 and 2, as they are "driver" patches, had to be
>>>> applied on USB tree (so Felipe's one), and the others (3 to 7) had to be
>>>> applied on STM32-DT tree (Alex's one). Did I miss something?
>>>
>>> patch 1 is documentation, right? Without the documentation patch,
>>> checkpatch will cringe :-) So either way works.
>>>
>>> If you insist, I can take 1-2 through my tree. No worries.
>>
>> I don't want to insist :) but for me it is better (and more safe) if you
>> take patch 1&2 in your tree, and will take others in mine.
>
> Okay, I'll apply 1&2
they are now in my testing/next and next branches.
--
balbi
WARNING: multiple messages have this Message-ID (diff)
From: felipe.balbi@linux.intel.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/7] Add support for USB OTG on STM32F7
Date: Thu, 12 Oct 2017 14:53:26 +0300 [thread overview]
Message-ID: <8760bk1t1l.fsf@linux.intel.com> (raw)
In-Reply-To: <878tgg1t5a.fsf@linux.intel.com>
Hi,
Felipe Balbi <felipe.balbi@linux.intel.com> writes:
>>>> I thought that patches 1 and 2, as they are "driver" patches, had to be
>>>> applied on USB tree (so Felipe's one), and the others (3 to 7) had to be
>>>> applied on STM32-DT tree (Alex's one). Did I miss something?
>>>
>>> patch 1 is documentation, right? Without the documentation patch,
>>> checkpatch will cringe :-) So either way works.
>>>
>>> If you insist, I can take 1-2 through my tree. No worries.
>>
>> I don't want to insist :) but for me it is better (and more safe) if you
>> take patch 1&2 in your tree, and will take others in mine.
>
> Okay, I'll apply 1&2
they are now in my testing/next and next branches.
--
balbi
next prev parent reply other threads:[~2017-10-12 11:53 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 14:20 [PATCHv2 0/7] Add support for USB OTG on STM32F7 Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-08-28 14:20 ` [PATCHv2 1/7] dt-bindings: usb: Document the STM32F7 DWC2 USB OTG HS core binding Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-09-01 15:35 ` Rob Herring
2017-09-01 15:35 ` Rob Herring
2017-09-01 15:35 ` Rob Herring
2017-08-28 14:20 ` [PATCHv2 2/7] usb: dwc2: add support for STM32F7 USB OTG HS Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-09-29 14:20 ` Amelie DELAUNAY
2017-09-29 14:20 ` Amelie DELAUNAY
2017-09-29 14:20 ` Amelie DELAUNAY
2017-09-30 17:16 ` John Youn
2017-09-30 17:16 ` John Youn
2017-09-30 17:16 ` John Youn
2017-08-28 14:20 ` [PATCHv2 3/7] ARM: dts: stm32: Add USB HS support for STM32F746 MCU Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-08-28 14:20 ` [PATCHv2 4/7] ARM: dts: stm32: Enable USB HS on stm32746g-eval Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-08-28 14:20 ` [PATCHv2 5/7] ARM: dts: stm32: Enable USB HS on stm32f746-disco Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-08-28 14:20 ` [PATCHv2 6/7] ARM: dts: stm32: Add USB FS support for STM32F746 MCU Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-08-28 14:20 ` [PATCHv2 7/7] ARM: dts: stm32: Enable USB FS on stm32f746-disco Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-08-28 14:20 ` Amelie Delaunay
2017-10-11 10:04 ` [PATCHv2 0/7] Add support for USB OTG on STM32F7 Felipe Balbi
2017-10-11 10:04 ` Felipe Balbi
2017-10-11 10:04 ` Felipe Balbi
2017-10-11 11:36 ` Alexandre Torgue
2017-10-11 11:36 ` Alexandre Torgue
2017-10-11 11:36 ` Alexandre Torgue
2017-10-11 11:50 ` Felipe Balbi
2017-10-11 11:50 ` Felipe Balbi
2017-10-11 11:50 ` Felipe Balbi
2017-10-11 12:05 ` Alexandre Torgue
2017-10-11 12:05 ` Alexandre Torgue
2017-10-11 12:05 ` Alexandre Torgue
2017-10-11 13:26 ` Felipe Balbi
2017-10-11 13:26 ` Felipe Balbi
2017-10-11 13:26 ` Felipe Balbi
2017-10-11 14:38 ` Alexandre Torgue
2017-10-11 14:38 ` Alexandre Torgue
2017-10-11 14:38 ` Alexandre Torgue
2017-10-12 8:32 ` Amelie DELAUNAY
2017-10-12 8:32 ` Amelie DELAUNAY
2017-10-12 8:32 ` Amelie DELAUNAY
2017-10-12 8:43 ` Felipe Balbi
2017-10-12 8:43 ` Felipe Balbi
2017-10-12 8:43 ` Felipe Balbi
2017-10-12 11:46 ` Alexandre Torgue
2017-10-12 11:46 ` Alexandre Torgue
2017-10-12 11:46 ` Alexandre Torgue
2017-10-12 11:51 ` Felipe Balbi
2017-10-12 11:51 ` Felipe Balbi
2017-10-12 11:51 ` Felipe Balbi
2017-10-12 11:53 ` Felipe Balbi [this message]
2017-10-12 11:53 ` Felipe Balbi
2017-10-12 11:53 ` Felipe Balbi
2017-10-12 12:01 ` Alexandre Torgue
2017-10-12 12:01 ` Alexandre Torgue
2017-10-12 12:01 ` Alexandre Torgue
2017-10-16 16:16 ` Alexandre Torgue
2017-10-16 16:16 ` Alexandre Torgue
2017-10-16 16:16 ` Alexandre Torgue
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=8760bk1t1l.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=alexandre.torgue@st.com \
--cc=amelie.delaunay@st.com \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=johnyoun@synopsys.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.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 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.