From: Felipe Balbi <balbi@kernel.org>
To: Doug Anderson <dianders@chromium.org>,
minas.harutyunyan@synopsys.com,
Terin Stock <terin@terinstock.com>
Cc: linux-usb@vger.kernel.org, Julius Werner <jwerner@chromium.org>,
Dmitry Torokhov <dtor@chromium.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] usb: dwc2: host: use hrtimer for NAK retries
Date: Wed, 05 Dec 2018 11:13:39 +0200 [thread overview]
Message-ID: <87zhtk1gl8.fsf@linux.intel.com> (raw)
In-Reply-To: <CAD=FV=UpPv3fWFjhrRRj1JjLPecbtzVYptVBkRaFHUgEm=isXw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
Hi,
Doug Anderson <dianders@chromium.org> writes:
> >> Signed-off-by: Terin Stock <terin@terinstock.com>
>> >> ---
>> >> drivers/usb/dwc2/hcd.h | 2 +-
>> >> drivers/usb/dwc2/hcd_queue.c | 19 ++++++++++++-------
>> >> 2 files changed, 13 insertions(+), 8 deletions(-)
>> >
>> > Reviewed-by: Douglas Anderson <dianders@chromium.org>
>> > Cc: stable@vger.kernel.org
>> >
>> Acked-by: Minas Harutyunyan <hminas@synopsys.com>
>
> It looks like Terin missed CCing you on the original patch. I assume
> you are still picking up dwc2 changes like this? If so, should he
> resend the patch targeting you (and including Minas and my tags) or do
> you want to pick it up from one of the mailing lists he CCed?
I'm picking it up, thanks
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2018-12-05 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 4:24 [PATCH v2] usb: dwc2: host: use hrtimer for NAK retries Terin Stock
2018-11-13 23:30 ` Doug Anderson
2018-11-21 7:16 ` Minas Harutyunyan
2018-11-21 16:11 ` Doug Anderson
2018-12-05 9:13 ` Felipe Balbi [this message]
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=87zhtk1gl8.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=dianders@chromium.org \
--cc=dtor@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=minas.harutyunyan@synopsys.com \
--cc=stable@vger.kernel.org \
--cc=terin@terinstock.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).