From: Tomi Valkeinen <tomi.valkeinen-l0cyMroinI0@public.gmane.org>
To: Kishon Vijay Abraham I <kishon-l0cyMroinI0@public.gmane.org>
Cc: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
balbi-l0cyMroinI0@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org,
eballetbo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
javier-0uQlZySMnqxg9hUCZPvPmw@public.gmane.org,
gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org
Subject: Re: [RFC PATCH 1/4] arm: omap: Add phy binding info for musb in plat data
Date: Fri, 14 Jun 2013 11:17:05 +0300 [thread overview]
Message-ID: <51BAD181.3020902@ti.com> (raw)
In-Reply-To: <20130614073314.GA20992-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
On 14/06/13 10:33, Tony Lindgren wrote:
> If we want to fix something this late in the merge window, the patches
> must have a clear description what caused the regression and what happens
> without the patches. These patches don't have that. And they are marked
> RFC also. So actually I'm not applying any of them before the regression
> descriptions are there and the patches have been reposted without RFC
> and have sufficient acks from people.
No disagreement there.
Kishon, I tested the patches on top of v3.10-rc5, booting with nfs root
via usb gadget eth:
Overo: works
Beagle: works, but I need to reconnect the usb cable after kernel is up
Beagle-xm: doesn't work. The cable is detected correctly, though
Panda: works
The problems with Beagles are there even without these patches, so they
do make things better (fix Overo).
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: tomi.valkeinen@ti.com (Tomi Valkeinen)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/4] arm: omap: Add phy binding info for musb in plat data
Date: Fri, 14 Jun 2013 11:17:05 +0300 [thread overview]
Message-ID: <51BAD181.3020902@ti.com> (raw)
In-Reply-To: <20130614073314.GA20992@atomide.com>
On 14/06/13 10:33, Tony Lindgren wrote:
> If we want to fix something this late in the merge window, the patches
> must have a clear description what caused the regression and what happens
> without the patches. These patches don't have that. And they are marked
> RFC also. So actually I'm not applying any of them before the regression
> descriptions are there and the patches have been reposted without RFC
> and have sufficient acks from people.
No disagreement there.
Kishon, I tested the patches on top of v3.10-rc5, booting with nfs root
via usb gadget eth:
Overo: works
Beagle: works, but I need to reconnect the usb cable after kernel is up
Beagle-xm: doesn't work. The cable is detected correctly, though
Panda: works
The problems with Beagles are there even without these patches, so they
do make things better (fix Overo).
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130614/152e5240/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Tony Lindgren <tony@atomide.com>, <balbi@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-usb@vger.kernel.org>, <linux@arm.linux.org.uk>,
<eballetbo@gmail.com>, <javier@dowhile0.org>,
<gregkh@linuxfoundation.org>
Subject: Re: [RFC PATCH 1/4] arm: omap: Add phy binding info for musb in plat data
Date: Fri, 14 Jun 2013 11:17:05 +0300 [thread overview]
Message-ID: <51BAD181.3020902@ti.com> (raw)
In-Reply-To: <20130614073314.GA20992@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
On 14/06/13 10:33, Tony Lindgren wrote:
> If we want to fix something this late in the merge window, the patches
> must have a clear description what caused the regression and what happens
> without the patches. These patches don't have that. And they are marked
> RFC also. So actually I'm not applying any of them before the regression
> descriptions are there and the patches have been reposted without RFC
> and have sufficient acks from people.
No disagreement there.
Kishon, I tested the patches on top of v3.10-rc5, booting with nfs root
via usb gadget eth:
Overo: works
Beagle: works, but I need to reconnect the usb cable after kernel is up
Beagle-xm: doesn't work. The cable is detected correctly, though
Panda: works
The problems with Beagles are there even without these patches, so they
do make things better (fix Overo).
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2013-06-14 8:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 13:22 [RFC PATCH 1/4] arm: omap: Add phy binding info for musb in plat data Kishon Vijay Abraham I
2013-05-17 13:22 ` Kishon Vijay Abraham I
2013-05-17 13:22 ` Kishon Vijay Abraham I
2013-05-17 13:22 ` [RFC PATCH 2/4] usb: phy: add a new API to get PHY ref by label Kishon Vijay Abraham I
2013-05-17 13:22 ` Kishon Vijay Abraham I
2013-05-17 13:22 ` Kishon Vijay Abraham I
2013-05-17 13:22 ` [RFC PATCH 3/4] usb: musb: omap: use the new API to get PHY reference " Kishon Vijay Abraham I
2013-05-17 13:22 ` Kishon Vijay Abraham I
2013-05-17 13:22 ` Kishon Vijay Abraham I
2013-05-17 13:22 ` [RFC PATCH 4/4] arm: omap: remove using usb_bind_phy for binding musb and phy Kishon Vijay Abraham I
2013-05-17 13:22 ` Kishon Vijay Abraham I
2013-05-17 13:22 ` Kishon Vijay Abraham I
2013-05-28 5:18 ` [RFC PATCH 1/4] arm: omap: Add phy binding info for musb in plat data Kishon Vijay Abraham I
2013-05-28 5:18 ` Kishon Vijay Abraham I
2013-05-28 5:18 ` Kishon Vijay Abraham I
2013-06-13 13:05 ` Tomi Valkeinen
2013-06-13 13:05 ` Tomi Valkeinen
2013-06-13 13:05 ` Tomi Valkeinen
2013-06-14 5:35 ` Kishon Vijay Abraham I
2013-06-14 5:35 ` Kishon Vijay Abraham I
2013-06-14 5:35 ` Kishon Vijay Abraham I
2013-06-14 5:47 ` Tony Lindgren
2013-06-14 5:47 ` Tony Lindgren
2013-06-14 6:36 ` Tomi Valkeinen
2013-06-14 6:36 ` Tomi Valkeinen
2013-06-14 6:36 ` Tomi Valkeinen
2013-06-14 7:33 ` Tony Lindgren
2013-06-14 7:33 ` Tony Lindgren
[not found] ` <20130614073314.GA20992-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2013-06-14 8:17 ` Tomi Valkeinen [this message]
2013-06-14 8:17 ` Tomi Valkeinen
2013-06-14 8:17 ` Tomi Valkeinen
2013-06-14 9:21 ` Kishon Vijay Abraham I
2013-06-14 9:21 ` Kishon Vijay Abraham I
2013-06-14 9:21 ` Kishon Vijay Abraham I
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=51BAD181.3020902@ti.com \
--to=tomi.valkeinen-l0cymroini0@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=eballetbo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=javier-0uQlZySMnqxg9hUCZPvPmw@public.gmane.org \
--cc=kishon-l0cyMroinI0@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@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 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.