From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Vivek Gautam <vivek.gautam@codeaurora.org>
Cc: kishon@ti.com, linux-kernel@vger.kernel.org,
Stephen Boyd <stephen.boyd@linaro.org>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v5 2/3] phy: Move ULPI phy header out of drivers to include path
Date: Thu, 11 May 2017 10:30:20 +0300 [thread overview]
Message-ID: <20170511073020.GA7676@kuha.fi.intel.com> (raw)
In-Reply-To: <1494485262-18995-2-git-send-email-vivek.gautam@codeaurora.org>
On Thu, May 11, 2017 at 12:17:41PM +0530, Vivek Gautam wrote:
> Although ULPI phy is currently being used by tusb1210,
> there can be other consumers too in future. So move this
> to the includes path for phy.
>
> Signed-off-by: Vivek Gautam <vivek.gautam@codeaurora.org>
> Cc: Stephen Boyd <stephen.boyd@linaro.org>
> Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> Cc: Kishon Vijay Abraham I <kishon@ti.com>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-omap@vger.kernel.org
> Cc: linux-usb@vger.kernel.org
> ---
Acked-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> Changes since v4:
> - None.
>
> Changes since v3:
> - Removed qcom phy changes, since patch - 1/3 addressed that now.
>
> Changes since v2:
> - Updated the location for this header in drivers using it.
>
> drivers/phy/phy-tusb1210.c | 3 +--
> {drivers => include/linux}/phy/ulpi_phy.h | 0
> 2 files changed, 1 insertion(+), 2 deletions(-)
> rename {drivers => include/linux}/phy/ulpi_phy.h (100%)
>
> diff --git a/drivers/phy/phy-tusb1210.c b/drivers/phy/phy-tusb1210.c
> index 4f6d5e71507d..bb3fb031c478 100644
> --- a/drivers/phy/phy-tusb1210.c
> +++ b/drivers/phy/phy-tusb1210.c
> @@ -12,8 +12,7 @@
> #include <linux/module.h>
> #include <linux/ulpi/driver.h>
> #include <linux/gpio/consumer.h>
> -
> -#include "ulpi_phy.h"
> +#include <linux/phy/ulpi_phy.h>
>
> #define TUSB1210_VENDOR_SPECIFIC2 0x80
> #define TUSB1210_VENDOR_SPECIFIC2_IHSTX_SHIFT 0
> diff --git a/drivers/phy/ulpi_phy.h b/include/linux/phy/ulpi_phy.h
> similarity index 100%
> rename from drivers/phy/ulpi_phy.h
> rename to include/linux/phy/ulpi_phy.h
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
--
heikki
next prev parent reply other threads:[~2017-05-11 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1494485262-18995-1-git-send-email-vivek.gautam@codeaurora.org>
2017-05-11 6:47 ` [PATCH v5 2/3] phy: Move ULPI phy header out of drivers to include path Vivek Gautam
2017-05-11 7:30 ` Heikki Krogerus [this message]
[not found] ` <1494485262-18995-1-git-send-email-vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-05-11 6:47 ` [PATCH v5 3/3] phy: Group vendor specific phy drivers Vivek Gautam
2017-05-12 8:45 ` Kishon Vijay Abraham I
2017-05-12 9:37 ` Vivek Gautam
2017-05-16 10:10 ` Kishon Vijay Abraham I
2017-05-17 3:43 ` Vivek Gautam
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=20170511073020.GA7676@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stephen.boyd@linaro.org \
--cc=vivek.gautam@codeaurora.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