From: Felipe Balbi <balbi@kernel.org>
To: Grigor Tovmasyan <Grigor.Tovmasyan@synopsys.com>Grigor Tovmasyan
<Grigor.Tovmasyan@synopsys.com>,
John Youn <John.Youn@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: [v1,10/14] usb: dwc2: Add dwc2_enter_hibernation(), dwc2_exit_hibernation()
Date: Mon, 12 Mar 2018 14:02:46 +0200 [thread overview]
Message-ID: <87tvtl8psp.fsf@linux.intel.com> (raw)
Hi,
Grigor Tovmasyan <Grigor.Tovmasyan@synopsys.com> writes:
> Hi Balbi,
>
> Did you tried to apply your patch of the top of your testing/next branch?
>
> If yes, could you please apply 01/14 ("[PATCH v1 01/14] usb: dwc2:
> Rename hibernation to partial_power_down")
> and 02/14 ([PATCH v1 02/14] usb: dwc2: Add hibernation field into
> dwc2_hw_params) patches right before 03/14 ([PATCH v1 03/14] usb: dwc2:
> gadget: Moved dtxfsiz backup array place).
>
> You can use "git rebase --interactive HEAD~10" command just adding
> following lines starting with "x" in the top of opened file.
>
> x git apply <01/14 patch>
> x git apply <02/14 patch>
> pick 3d6c862d9361 usb: dwc2: gadget: Moved dtxfsiz backup array place
if I do that, patch 6/14 won't apply anymore. I've pushed a 'tmp' branch
to kernel.org with patches 1/14 - 5/14 on top of my 'next' branch. Now
6/14 doesn't apply to that.
next reply other threads:[~2018-03-12 12:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 12:02 Felipe Balbi [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-12 14:12 [v1,10/14] usb: dwc2: Add dwc2_enter_hibernation(), dwc2_exit_hibernation() Felipe Balbi
2018-03-12 13:39 Grigor Tovmasyan
2018-03-12 13:33 Felipe Balbi
2018-03-12 13:16 Grigor Tovmasyan
2018-03-12 13:06 Felipe Balbi
2018-03-12 12:59 Grigor Tovmasyan
2018-03-12 12:47 Felipe Balbi
2018-03-12 12:12 Grigor Tovmasyan
2018-03-12 11:55 Grigor Tovmasyan
2018-03-12 10:22 Felipe Balbi
2018-03-09 13:42 Grigor Tovmasyan
2018-03-09 13:10 Grigor Tovmasyan
2018-03-09 9:07 Felipe Balbi
2018-02-16 10:10 Grigor Tovmasyan
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=87tvtl8psp.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=Grigor.Tovmasyan@synopsys.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 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.