From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org>,
Venu Byravarasu
<vbyravarasu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: Linux USB Mailing List
<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Alan Stern
<stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>,
Greg KH
<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RESEND/PATCH] usb: host: ehci-tegra: fix PHY error handling
Date: Thu, 21 Mar 2013 11:19:51 -0600 [thread overview]
Message-ID: <514B4137.2020707@wwwdotorg.org> (raw)
In-Reply-To: <1363868603-14525-1-git-send-email-balbi-l0cyMroinI0@public.gmane.org>
On 03/21/2013 06:23 AM, Felipe Balbi wrote:
> PHY layer no longer returns NULL, we must
> switch from IS_ERR_OR_NULL() to IS_ERR().
The patches that I'll put into my topic branch are not yet complete;
Venu first posted them a couple days back and there are a number of
issues that will require a repost.
I would suggest that you apply your patch to your tree, and when Venu
reposts his patches, he'll need to make sure he's rebased on top of this
patch.
Venu, just so you're clear: The device tree changes in your series (the
first 2 or 3 patches) will be applied to a branch based directly to
v3.9-rc1, which will then get merged into both Felipe's USB tree and the
Tegra tree. The USB driver changes in your series will then be applied
to Felipe's USB branch, so please make sure they apply there. Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-03-21 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 12:23 [RESEND/PATCH] usb: host: ehci-tegra: fix PHY error handling Felipe Balbi
[not found] ` <1363868603-14525-1-git-send-email-balbi-l0cyMroinI0@public.gmane.org>
2013-03-21 17:19 ` Stephen Warren [this message]
[not found] ` <514B4137.2020707-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-03-21 17:31 ` Felipe Balbi
[not found] ` <20130321173100.GB16186-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-03-21 17:37 ` Stephen Warren
[not found] ` <514B4544.4090904-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-03-21 18:14 ` Felipe Balbi
2013-04-02 8:36 ` Felipe Balbi
[not found] ` <20130402083604.GJ30286-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-04-02 15:33 ` Stephen Warren
[not found] ` <515AFA64.3050107-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-04-02 15:44 ` Felipe Balbi
[not found] ` <20130402154410.GL22014-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-04-02 17:39 ` Sergei Shtylyov
[not found] ` <515B17ED.7010709-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2013-04-02 18:00 ` 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=514B4137.2020707@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org \
--cc=vbyravarasu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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