From: Jiri Slaby <jslaby@suse.cz>
To: balbi@ti.com, gregkh@linuxfoundation.org
Cc: b-liu@ti.com, stable@vger.kernel.org
Subject: Re: [PATCH] usb: musb: use new USB_RESUME_TIMEOUT
Date: Tue, 05 May 2015 09:17:38 +0200 [thread overview]
Message-ID: <55486E92.3000704@suse.cz> (raw)
In-Reply-To: <20150504151518.GA6072@saruman.tx.rr.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 05/04/2015, 05:15 PM, Felipe Balbi wrote:
> From: Felipe Balbi <balbi@ti.com>
>
> commit 309be239369609929d5d3833ee043f7c5afc95d1 upstream.
>
> Make sure we're using the new macro, so our resume signaling will
> always pass certification.
>
> Based on original work by Bin Liu <Bin Liu <b-liu@ti.com>>
Which trees do you want us to apply these three?
thanks,
- --
js
suse labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJVSG6QAAoJEL0lsQQGtHBJIaIQAJqef5yCoh6kDPT4dhq7xcn7
Bkl/o1teJptHS5yFXkhJ5hf5zlK7GaUe94OtciDZ1uL3KqXMWGAtBuf6bD2/OaAB
v6n4+NtLOmURgxNdFWLkSeBpHbNarPA6AhYwpaQWY/YTtuw3JhQ4LubSaaI0VqlZ
9ACrYAYOimjpC17XubVDDG0AaCz1LycKM3ORq6E7sxb7zUlF/yBlam/e/xW0OqfE
5laH8Yc8uaRoyQGmhgCtMxsb/uFroLXSrRgGxAKER1t39vzdHr+tZIIo2Y890Hlu
jIZaNk8B3kwcHe3VpmrxfNtuI0M4oF/yBxBUuomlxnFLYJDYcE/GEx8MI+74Fg91
K+5svGBOollzHnJ+KWXheLz1rOryhGtPEw/7GDD5uF3laJc84VOO+/3ebA1vlcfE
CzpfAcMkm8Fwqnza5Ewg9g5BaQ+XK7gUHeN1jSlFfnymDC9MJGxfm0HwnbxJd3zb
BlP1ePmXqqKS9mYrFbv7t0gBjSl3rcxUyL9bSXEtsrBsjAURKZGc3txqs1ph5osJ
bLGMMLDU2Ro6ZVSQY/GyzJ/6OeOK4b/F3elUrAUW0mCkxtll5rHTITouvCgl7ykI
oaGo3qrUuGrHBn+etkFDTNW/onoOXt/P15ZDWJjNFqGS5XQSyKR/xlFO5SN0/qGR
hQS7nMADsrRsra/u/RS+
=LaWr
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-05-05 7:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 13:14 FAILED: patch "[PATCH] usb: musb: use new USB_RESUME_TIMEOUT" failed to apply to 3.14-stable tree gregkh
2015-05-04 15:15 ` [PATCH] usb: musb: use new USB_RESUME_TIMEOUT Felipe Balbi
2015-05-05 7:17 ` Jiri Slaby [this message]
2015-05-05 14:33 ` Felipe Balbi
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=55486E92.3000704@suse.cz \
--to=jslaby@suse.cz \
--cc=b-liu@ti.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.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 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.