From: Philipp Zabel <p.zabel@pengutronix.de>
To: Felipe Balbi <balbi@kernel.org>, linux-kernel@vger.kernel.org
Cc: Vivek Gautam <vivek.gautam@codeaurora.org>,
Jon Hunter <jonathanh@nvidia.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thierry Reding <treding@nvidia.com>,
linux-tegra@vger.kernel.org, linux-usb@vger.kernel.org,
linux-arm-msm@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH v7 3/4] usb: dwc3: of-simple: Add support to get resets for the device
Date: Thu, 19 Oct 2017 13:47:26 +0200 [thread overview]
Message-ID: <1508413646.7665.8.camel@pengutronix.de> (raw)
In-Reply-To: <87shefgyqc.fsf@linux.intel.com>
On Thu, 2017-10-19 at 14:31 +0300, Felipe Balbi wrote:
> Hi,
>
> Philipp Zabel <p.zabel@pengutronix.de> writes:
> > Hi Felipe,
> >
> > On Thu, 2017-10-19 at 12:38 +0300, Felipe Balbi wrote:
> > > Philipp Zabel <p.zabel@pengutronix.de> writes:
> > >
> > > > From: Vivek Gautam <vivek.gautam@codeaurora.org>
> > > >
> > > > Add support to get a list of resets available for the device.
> > > > These resets must be kept de-asserted until the device is
> > > > in use.
> > > >
> > > > Cc: Felipe Balbi <balbi@kernel.org>
> > > > Signed-off-by: Vivek Gautam <vivek.gautam@codeaurora.org>
> > > > [p.zabel@pengutronix.de: switch to hidden reset control array]
> > > > Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> > >
> > > now this seems like it depends on patch 1/4, right? Is the reset API
> > > change going on v4.15?
> >
> > Thank you for the reminder. Patch 1 has made it into v4.14-rc1, commit
> > 17c82e206d2a ("reset: Add APIs to manage array of resets"). The other
> > patches could be picked up for v4.15 without any dependency issues.
>
> patch 2 applied fine. patch 3 fails to apply hunk 2.
>
> checking file drivers/usb/dwc3/dwc3-of-simple.c
> Hunk #1 succeeded at 28 (offset -1 lines).
> Hunk #2 FAILED at 98.
> 1 out of 5 hunks FAILED
>
>
> Care to rebase on my testing/next?
Thanks, I'll resend patch 3 separately.
regards
Philipp
next prev parent reply other threads:[~2017-10-19 11:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 15:59 [PATCH v7 0/4] reset: APIs to manage a list of resets Philipp Zabel
2017-07-19 15:59 ` [PATCH v7 1/4] reset: Add APIs to manage array " Philipp Zabel
2017-10-19 18:54 ` Bjorn Andersson
2017-10-20 12:20 ` Philipp Zabel
2017-11-01 22:24 ` Bjorn Andersson
2017-11-02 12:57 ` Philipp Zabel
2017-07-19 15:59 ` [PATCH v7 2/4] usb: dwc3: of-simple: Re-order resource handling in remove Philipp Zabel
2017-10-19 9:36 ` Felipe Balbi
2017-07-19 15:59 ` [PATCH v7 3/4] usb: dwc3: of-simple: Add support to get resets for the device Philipp Zabel
2017-10-19 9:38 ` Felipe Balbi
2017-10-19 10:45 ` Philipp Zabel
2017-10-19 11:30 ` Felipe Balbi
2017-10-19 11:31 ` Felipe Balbi
2017-10-19 11:47 ` Philipp Zabel [this message]
2017-07-19 15:59 ` [PATCH v7 4/4] soc/tegra: pmc: Use the new reset APIs to manage reset controllers Philipp Zabel
2017-10-19 15:17 ` Philipp Zabel
2017-10-20 15:51 ` Jon Hunter
2017-10-23 9:20 ` Philipp Zabel
2018-03-09 8:09 ` Thierry Reding
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=1508413646.7665.8.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=treding@nvidia.com \
--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
Powered by JetHome