From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] char: tile-srom: Remove reference to platform_bus
Date: Tue, 5 Aug 2014 16:06:54 -0700 [thread overview]
Message-ID: <20140805230654.GA24614@kroah.com> (raw)
In-Reply-To: <53E139C8.9000502@tilera.com>
On Tue, Aug 05, 2014 at 04:08:40PM -0400, Chris Metcalf wrote:
> On 8/1/2014 1:21 PM, Pawel Moll wrote:
> >On Thu, 2014-07-31 at 21:24 +0100, Chris Metcalf wrote:
> >>On 7/25/2014 10:23 AM, Pawel Moll wrote:
> >>>The code was creating "srom" class devices using
> >>>platform_bus as a parent. As they are not really
> >>>platform devices, make them virtual, using NULL instead.
> >>>
> >>>Cc: Chris Metcalf<cmetcalf@tilera.com>
> >>>Signed-off-by: Pawel Moll<pawel.moll@arm.com>
> >>>---
> >>> drivers/char/tile-srom.c | 2 +-
> >>> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>Can you clarify the point of this change a bit?
> >Theoretically speaking there shouldn't be any need to export the
> >platform bus root, as all devices should be registered via the platform
> >API (platform_device_register & co.)
>
> So, perhaps the right fix is to just use platform_device_register()
> etc for this device, rather than making it virtual?
Sure, that's fine with me if you want to make it a platform device, but
note that a platform device doesn't have a minor associated with it, you
will have to still have your existing srom_class and the rest. Right
now you aren't creating any real "devices" in the kernel, other than the
one you use for your minor number, which is not a "real" device.
struct srom_dev should be a platform device and then this will get
"easier" overall, sorry I missed that when the original code was
submitted.
thanks,
greg k-h
next prev parent reply other threads:[~2014-08-05 23:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 14:23 [PATCH 1/5] ARM: imx: Remove references to platform_bus in mxc code Pawel Moll
2014-07-25 14:23 ` [PATCH 2/5] char: tile-srom: Remove reference to platform_bus Pawel Moll
2014-07-31 20:24 ` Chris Metcalf
2014-07-31 21:32 ` Greg Kroah-Hartman
2014-08-01 17:21 ` Pawel Moll
2014-08-05 20:08 ` Chris Metcalf
2014-08-05 23:06 ` Greg Kroah-Hartman [this message]
2014-08-08 16:34 ` Pawel Moll
2014-08-08 16:39 ` Pawel Moll
2014-08-11 2:38 ` Chris Metcalf
2014-08-29 18:43 ` Chris Metcalf
2014-09-01 12:27 ` Pawel Moll
2014-09-01 13:53 ` Chris Metcalf
2014-07-25 14:23 ` [PATCH 3/5] mmc: sdhci-pltfm: Do not use parent as the host's device Pawel Moll
2014-08-08 16:36 ` Pawel Moll
2014-08-11 9:07 ` Ulf Hansson
2014-08-11 9:15 ` Pawel Moll
2014-08-11 9:32 ` Ulf Hansson
2014-08-12 8:58 ` Ulf Hansson
2014-08-11 10:02 ` Russell King - ARM Linux
2014-07-25 14:23 ` [PATCH 4/5] [SCSI] Do not use platform_bus as a parent Pawel Moll
2014-07-25 14:46 ` James Bottomley
2014-07-25 15:40 ` Pawel Moll
2014-07-26 20:11 ` Greg Kroah-Hartman
2014-07-27 3:52 ` James Bottomley
2014-07-27 15:07 ` Greg Kroah-Hartman
2014-08-01 17:25 ` Pawel Moll
2014-07-25 14:23 ` [PATCH 5/5] platform: Make platform_bus device a platform device Pawel Moll
2014-07-26 20:12 ` Greg Kroah-Hartman
2014-08-01 17:21 ` Pawel Moll
2014-07-26 20:13 ` Greg Kroah-Hartman
2014-08-01 17:21 ` Pawel Moll
2014-07-28 1:45 ` [PATCH 1/5] ARM: imx: Remove references to platform_bus in mxc code Shawn Guo
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=20140805230654.GA24614@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).