From: Greg KH <gregkh@linuxfoundation.org>
To: Felipe Balbi <balbi@ti.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
tony@atomide.com, linux@arm.linux.org.uk, eballetbo@gmail.com,
javier@dowhile0.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 2/2] arm: omap: remove *.auto* from device names given in usb_bind_phy
Date: Tue, 30 Jul 2013 07:25:17 -0700 [thread overview]
Message-ID: <20130730142517.GA29015@kroah.com> (raw)
In-Reply-To: <20130730081520.GH16441@radagast>
On Tue, Jul 30, 2013 at 11:15:20AM +0300, Felipe Balbi wrote:
> > > look at Greg's and my reply to that email.
> >
> > but finally Greg agreed to what Tomasz proposed no?
>
> that's not what I see in the thread. I see Greg agreed to regulator's
> own IDs being sequentially created, but he mentions device names can
> change.
And that no one should _ever_ rely on them to be a specific "name", the
bus is responsible for creating the id, it could be "random" and
everything should work just fine.
thanks,
greg k-h
prev parent reply other threads:[~2013-07-30 14:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 9:03 [PATCH 0/2] usb: fix controller-PHY binding for OMAP3 platform Kishon Vijay Abraham I
2013-07-26 9:03 ` [PATCH 1/2] usb: musb: omap: remove using PLATFORM_DEVID_AUTO in omap2430.c Kishon Vijay Abraham I
2013-07-26 9:03 ` [PATCH 2/2] arm: omap: remove *.auto* from device names given in usb_bind_phy Kishon Vijay Abraham I
2013-07-29 15:06 ` Felipe Balbi
2013-07-29 15:29 ` Kishon Vijay Abraham I
2013-07-29 17:54 ` Felipe Balbi
2013-07-30 5:14 ` Kishon Vijay Abraham I
2013-07-30 6:01 ` Felipe Balbi
2013-07-30 6:11 ` Kishon Vijay Abraham I
2013-07-30 6:18 ` Felipe Balbi
2013-07-30 6:25 ` Kishon Vijay Abraham I
2013-07-30 6:28 ` Felipe Balbi
2013-07-30 6:46 ` Kishon Vijay Abraham I
2013-07-30 7:16 ` Felipe Balbi
2013-07-30 8:11 ` Kishon Vijay Abraham I
2013-07-30 8:15 ` Felipe Balbi
2013-07-30 14:25 ` Greg KH [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=20130730142517.GA29015@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@ti.com \
--cc=eballetbo@gmail.com \
--cc=javier@dowhile0.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.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