From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [RFC] driver-core: Remove dummy 'platform_bus'
Date: Wed, 21 Nov 2012 06:52:39 -0800 [thread overview]
Message-ID: <20121121145239.GA21860@kroah.com> (raw)
In-Reply-To: <1353509071-8658-1-git-send-email-grant.likely@secretlab.ca>
On Wed, Nov 21, 2012 at 02:44:31PM +0000, Grant Likely wrote:
> The "platform_bus" (note: not platform_bus_type) only exists as an empty
> directory to put platform devices into. However, it really doesn't make
> sense to segregate all the platform devices into a sub directory when
> typically they are memory mapped devices that doen't go through any
> particular bus. Particularly on embedded type platforms the platform_bus
> directory doesn't add anything.
>
> However, this will probably just end up breaking some userspace that
> depends on the /sys/devices/platform/ path to be present (no matter how
> much we protest that userspace must not depend on paths in sysfs). So
> while I'm seriously proposing this change, it may just be unacceptable
> ABI breakage
If the devices don't show up under platform/ where are they going to be
at now, virtual/ ? That doesn't sound like a good plan, they should be
somewhere "useful".
And yes, odds are this will break userspace, but we might not know until
we try it, have you tried it on different distros to see what happens?
thanks,
greg k-h
next prev parent reply other threads:[~2012-11-21 14:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 14:44 [RFC] driver-core: Remove dummy 'platform_bus' Grant Likely
2012-11-21 14:52 ` Greg Kroah-Hartman [this message]
2012-11-22 19:17 ` Kay Sievers
2012-11-22 21:20 ` Grant Likely
2012-11-23 14:39 ` Kay Sievers
2014-04-21 21:05 ` Rob Herring
2014-04-23 14:05 ` Grant Likely
2014-04-23 14:16 ` Rob Herring
2014-04-23 14:49 ` Grant Likely
2014-04-23 14:44 ` Grant Likely
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=20121121145239.GA21860@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=grant.likely@secretlab.ca \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@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.