From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
To: Rob Herring <robh@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Peter Chen <peter.chen@freescale.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Daniel Tang <dt.tangr@gmail.com>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH v3 4/6] dt-bindings: Consolidate ChipIdea USB ci13xxx bindings
Date: Mon, 01 Jun 2015 10:09:47 +0300 [thread overview]
Message-ID: <1433142587.6844.11.camel@mm-sol.com> (raw)
In-Reply-To: <1432917526-9688-5-git-send-email-robh@kernel.org>
On Fri, 2015-05-29 at 11:38 -0500, Rob Herring wrote:
> Combine the ChipIdea USB binding into a single document to reduce
> duplication and fragmentation. This marks use of the old PHY bindings as
> deprecated. Future compatible bindings should use generic PHY binding.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> Cc: Ivan T. Ivanov <iivanov@mm-sol.com>
> Cc: Peter Chen chen@freescale.com>
> Cc: Daniel Tang tangr@gmail.com>
> Cc: Pawel Moll moll@arm.com>
> Cc: Mark Rutland rutland@arm.com>
> Cc: Ian Campbell <ijc+devicetree@hellion.org.uk>
> Cc: Kumar Gala <galak@codeaurora.org>
> Cc: devicetree@vger.kernel.org
> ---
> .../devicetree/bindings/usb/ci-hdrc-imx.txt | 35 ----------------------
> .../devicetree/bindings/usb/ci-hdrc-qcom.txt | 17 -----------
> .../devicetree/bindings/usb/ci-hdrc-usb2.txt | 22 +++++++++++++-
> .../devicetree/bindings/usb/ci-hdrc-zevio.txt | 17 -----------
> 4 files changed, 21 insertions(+), 70 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/usb/ci-hdrc-imx.txt
> delete mode 100644 Documentation/devicetree/bindings/usb/ci-hdrc-qcom.txt
> delete mode 100644 Documentation/devicetree/bindings/usb/ci-hdrc-zevio.txt
Thanks. For Qualcomm part:
Acked-by: Ivan T. Ivanov <iivanov@mm-sol.com>
next prev parent reply other threads:[~2015-06-01 7:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 16:38 [PATCH v3 0/6] Marvell PXA1928 USB support Rob Herring
2015-05-29 16:38 ` [PATCH v3 1/6] dt-bindings: Add Marvell PXA1928 USB and HSIC PHY bindings Rob Herring
2015-05-29 16:38 ` [PATCH v3 2/6] phy: Add Marvell USB 2.0 OTG 28nm PHY Rob Herring
2015-05-29 16:38 ` [PATCH v3 3/6] phy: add Marvell HSIC " Rob Herring
2015-05-29 16:38 ` [PATCH v3 4/6] dt-bindings: Consolidate ChipIdea USB ci13xxx bindings Rob Herring
2015-06-01 7:09 ` Ivan T. Ivanov [this message]
2015-06-05 6:22 ` Peter Chen
2015-05-29 16:38 ` [PATCH v3 5/6] usb: chipidea: allow multiple instances to use default ci_default_pdata Rob Herring
2015-06-05 6:32 ` Peter Chen
2015-05-29 16:38 ` [PATCH v3 6/6] usb: chipidea: add work-around for Marvell HSIC PHY startup Rob Herring
2015-06-05 6:32 ` Peter Chen
2015-06-09 19:22 ` [PATCH v3 0/6] Marvell PXA1928 USB support Greg Kroah-Hartman
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=1433142587.6844.11.camel@mm-sol.com \
--to=iivanov@mm-sol.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=dt.tangr@gmail.com \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=peter.chen@freescale.com \
--cc=robh@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