From: Felipe Balbi <balbi@kernel.org>
To: 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>
Cc: Stefan Wahren <stefan.wahren@i2se.com>
Subject: [6/6] usb: dwc2: Force mode optimizations
Date: Fri, 16 Feb 2018 09:08:35 +0200 [thread overview]
Message-ID: <87zi4976oc.fsf@linux.intel.com> (raw)
Hi,
Grigor Tovmasyan <Grigor.Tovmasyan@synopsys.com> writes:
> Hi Balbi,
>
> I rebased this commit to your testing/next (see below).
Are you sure you did?
checking file drivers/usb/dwc2/core.c
Hunk #1 FAILED at 367.
Hunk #2 FAILED at 391.
Hunk #3 FAILED at 403.
Hunk #4 FAILED at 425.
Hunk #5 FAILED at 441.
Hunk #6 FAILED at 455.
Hunk #7 succeeded at 481 with fuzz 2.
Hunk #8 FAILED at 718.
7 out of 8 hunks FAILED
checking file drivers/usb/dwc2/core.h
Hunk #1 FAILED at 1116.
1 out of 1 hunk FAILED
checking file drivers/usb/dwc2/hcd.c
Hunk #1 FAILED at 141.
Hunk #2 FAILED at 239.
Hunk #3 FAILED at 2270.
3 out of 3 hunks FAILED
checking file drivers/usb/dwc2/params.c
Hunk #1 FAILED at 593.
Hunk #2 FAILED at 620.
Hunk #3 FAILED at 639.
3 out of 3 hunks FAILED
checking file drivers/usb/dwc2/platform.c
Hunk #1 FAILED at 427.
1 out of 1 hunk FAILED
And this is after fixing your malformed patch with mangled lines. Please
rebase again and use git send-email. For reference, My testing/next is @
08900d3304bb787164e79a8942112208917d1ddd
next reply other threads:[~2018-02-16 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 7:08 Felipe Balbi [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-16 8:56 [6/6] usb: dwc2: Force mode optimizations Grigor Tovmasyan
2018-02-16 8:18 Grigor Tovmasyan
2018-02-15 16:34 Grigor Tovmasyan
2018-01-16 12:05 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=87zi4976oc.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=Grigor.Tovmasyan@synopsys.com \
--cc=John.Youn@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=stefan.wahren@i2se.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;
as well as URLs for NNTP newsgroup(s).