From: Felipe Balbi <balbi@ti.com>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: balbi <balbi@ti.com>, "Kiran Raparthy" <kiran.kumar@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
"John Stultz" <john.stultz@linaro.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-usb <linux-usb@vger.kernel.org>,
"Android Kernel Team" <kernel-team@android.com>,
"Arve Hj�nnev�g" <arve@android.com>,
"Benoit Goby" <benoit@android.com>,
"Todd Poynor" <toddpoynor@google.com>
Subject: Re: [PATCH v1 2/3] usb: phy: Handle per-PHY event for connect and disconnect events
Date: Mon, 24 Nov 2014 10:21:43 -0600 [thread overview]
Message-ID: <20141124162143.GI20705@saruman> (raw)
In-Reply-To: <CAO_48GFK_a=d+jUMR8-eqRVy1V_hSt8hKs2uOA00zzxstgV7pA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3842 bytes --]
Hi,
On Mon, Nov 24, 2014 at 09:45:35PM +0530, Sumit Semwal wrote:
> On 24 November 2014 at 21:24, Felipe Balbi <balbi@ti.com> wrote:
> > On Mon, Nov 24, 2014 at 09:19:09PM +0530, Sumit Semwal wrote:
> >> Hi Felipe,
> >>
> >> On 24 November 2014 at 20:08, Felipe Balbi <balbi@ti.com> wrote:
> >> > Hi,
> >> >
> >> > On Fri, Nov 21, 2014 at 09:13:00PM +0530, Kiran Raparthy wrote:
> >> >> On 21 November 2014 20:41, Felipe Balbi <balbi@ti.com> wrote:
> >> >> > On Fri, Nov 21, 2014 at 11:31:21AM +0530, Kiran Raparthy wrote:
> >> >> >> usb: phy: Handle per-PHY event for connnect and disconnect events
> >> >> >>
> >> >> >> When usb is connected and enumerated in device mode or when usb is
> >> >> >> disconnected,call usb_phy_set_event from phy drivers to handle per-PHY event.
> >> >> >>
> >> >> >> Cc: Felipe Balbi <balbi@ti.com>
> >> >> >> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >> >> >> Cc: linux-kernel@vger.kernel.org
> >> >> >> Cc: linux-usb@vger.kernel.org
> >> >> >> Cc: Android Kernel Team <kernel-team@android.com>
> >> >> >> Cc: John Stultz <john.stultz@linaro.org>
> >> >> >> Cc: Sumit Semwal <sumit.semwal@linaro.org>
> >> >> >> Cc: Arve Hj�nnev�g <arve@android.com>
> >> >> >> Cc: Benoit Goby <benoit@android.com>
> >> >> >> [Original patch in Android from Todd]
> >> >> >> Cc: Todd Poynor <toddpoynor@google.com>
> >> >> >> Signed-off-by: Kiran Raparthy <kiran.kumar@linaro.org>
> >> >> >
> >> >> > this patch doesn't apply, please rebase entire series on my testing/next.
> >> >
> >> > your rebased version didn't apply either. Can you make sure you're
> >> > rebasing on top of my today's testing/next branch ?
> >> >
> >> I just verified that I am able to apply both this patch (and the next
> >> one - so 2/3 and 3/3) on your testing/next branch - just to make sure,
> >> this is the git/branch right?
> >>
> >> https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
> >> branch:testing/next
> >
> > that's the correct branch, but here's what I get:
>
> That's very odd - I pulled your branch for the first time about 5
> minutes before I sent the mail? perhaps local branch updates?
$ git show
commit c9d655dccea0cb6df20ba5b39294a24be045ea4f
Author: Fabio Estevam <fabio.estevam@freescale.com>
Date: Wed Nov 19 12:37:53 2014 -0200
usb: dwc2: Fix build warning when CONFIG_PM_SLEEP=n
Building with bcm2835_defconfig, which has CONFIG_PM_SLEEP=n causes the
following build warning:
drivers/usb/dwc2/platform.c:227:12: warning: 'dwc2_suspend' defined but not used [-Wunused-function]
drivers/usb/dwc2/platform.c:237:12: warning: 'dwc2_resume' defined but not used [-Wunused-function]
Annotate these functions with '__maybe_unused' to prevent the warnings.
Reported-by: Olof's autobuilder <build@lixom.net>
Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
diff --git a/drivers/usb/dwc2/platform.c b/drivers/usb/dwc2/platform.c
index ec5658a..6a795aa 100644
--- a/drivers/usb/dwc2/platform.c
+++ b/drivers/usb/dwc2/platform.c
@@ -226,7 +226,7 @@ static int dwc2_driver_probe(struct platform_device *dev)
return retval;
}
-static int dwc2_suspend(struct device *dev)
+static int __maybe_unused dwc2_suspend(struct device *dev)
{
struct dwc2_hsotg *dwc2 = dev_get_drvdata(dev);
int ret = 0;
@@ -236,7 +236,7 @@ static int dwc2_suspend(struct device *dev)
return ret;
}
-static int dwc2_resume(struct device *dev)
+static int __maybe_unused dwc2_resume(struct device *dev)
{
struct dwc2_hsotg *dwc2 = dev_get_drvdata(dev);
int ret = 0;
that's the head of my branch, which is testing/next. And I don't have
anything in my index:
$ git diff
$ echo $?
0
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-24 16:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 6:01 [PATCH v1 0/3] usb: phy: hold wakeupsource on usb phy events Kiran Raparthy
2014-11-21 6:01 ` [PATCH v1 1/3] usb: phy: introduce usb_phy_set_event interface Kiran Raparthy
2014-11-21 6:01 ` [PATCH v1 2/3] usb: phy: Handle per-PHY event for connect and disconnect events Kiran Raparthy
2014-11-21 15:11 ` Felipe Balbi
2014-11-21 15:43 ` Kiran Raparthy
2014-11-24 14:38 ` Felipe Balbi
2014-11-24 15:49 ` Sumit Semwal
2014-11-24 15:54 ` Felipe Balbi
2014-11-24 16:15 ` Sumit Semwal
2014-11-24 16:21 ` Felipe Balbi [this message]
2014-11-21 6:01 ` [PATCH v1 3/3] usb: phy: hold wakeupsource when USB is enumerated in peripheral mode Kiran Raparthy
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=20141124162143.GI20705@saruman \
--to=balbi@ti.com \
--cc=arve@android.com \
--cc=benoit@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=kiran.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=toddpoynor@google.com \
/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