From: Greg KH <gregkh@suse.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Patrick Pannuto <ppannuto@quicinc.com>,
Patrick Pannuto <ppannuto@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"damm@opensource.se" <damm@opensource.se>,
"lethal@linux-sh.org" <lethal@linux-sh.org>,
"rjw@sisk.pl" <rjw@sisk.pl>, "dtor@mail.ru" <dtor@mail.ru>,
"eric.y.miao@gmail.com" <eric.y.miao@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Kevin Hilman <khilman@deeprootsystems.com>
Subject: Re: [RFC PATCH] platform: Faciliatate the creation of pseduo-platform busses
Date: Tue, 10 Aug 2010 16:53:23 -0700 [thread overview]
Message-ID: <20100810235323.GA24612@suse.de> (raw)
In-Reply-To: <AANLkTimjXd=SL61KvjDfvJ-JtXsSVW9pwOYBFUHX0mVp@mail.gmail.com>
On Sat, Aug 07, 2010 at 11:28:13AM -0600, Grant Likely wrote:
> On Sat, Aug 7, 2010 at 12:35 AM, Grant Likely <grant.likely@secretlab.ca> wrote:
> > On Fri, Aug 6, 2010 at 5:46 PM, Greg KH <gregkh@suse.de> wrote:
> >> That would be nice, but take your "standard" PC today:
> >> > ls /sys/devices/platform/
> >> Fixed MDIO bus.0 i8042 pcspkr power serial8250 uevent vesafb.0
> >>
> >> There are tty devices below the serial port, which is nice to see, but
> >> the others? I don't know what type of bus they would be on, do you?
> [...]
> > I wouldn't have any problem modifying those specific drivers to
> > register under something like /sys/devices/legacy, but I don't really
> > think it is in any way necessary.
>
> Or for that matter, make those drivers explicitly use
> /sys/devices/platform so that I don't cause churn on PCs. :-) I'd
> like to be rid of it as default behaviour for embedded though.
Yes, that would be the easier (and better) solution.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-08-10 23:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 23:35 [RFC PATCH] platform: Faciliatate the creation of pseduo-platform busses Patrick Pannuto
2010-08-03 23:36 ` Patrick Pannuto
2010-08-03 23:56 ` Greg KH
2010-08-04 0:02 ` Patrick Pannuto
2010-08-04 0:09 ` Greg KH
2010-08-04 0:17 ` Patrick Pannuto
2010-08-04 0:41 ` Timothy Meade
2010-08-05 22:59 ` Grant Likely
2010-08-06 14:27 ` Greg KH
2010-08-06 15:12 ` Grant Likely
2010-08-06 23:46 ` Greg KH
2010-08-07 6:35 ` Grant Likely
2010-08-07 17:28 ` Grant Likely
2010-08-10 23:53 ` Greg KH [this message]
2010-08-05 23:00 ` Grant Likely
2010-08-04 9:37 ` Alan Cox
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=20100810235323.GA24612@suse.de \
--to=gregkh@suse.de \
--cc=damm@opensource.se \
--cc=dtor@mail.ru \
--cc=eric.y.miao@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=khilman@deeprootsystems.com \
--cc=lethal@linux-sh.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ppannuto@codeaurora.org \
--cc=ppannuto@quicinc.com \
--cc=rjw@sisk.pl \
/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).