From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pantelis Antoniou <panto@antoniou-consulting.com>
Cc: linux-kernel@vger.kernel.org, Matt Porter <mporter@ti.com>,
Russ Dill <Russ.Dill@ti.com>,
Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH] platform: Fix platform device resource linking
Date: Thu, 17 Jan 2013 19:00:17 -0800 [thread overview]
Message-ID: <20130118030017.GA11423@kroah.com> (raw)
In-Reply-To: <87DCB3B7-0A5A-42F0-BF9C-0E91B56960C6@antoniou-consulting.com>
On Thu, Jan 17, 2013 at 07:27:21PM +0200, Pantelis Antoniou wrote:
> >> In a nutshell, we have to exercise the platform device subsystem, in ways
> >> that never happened before, so all sorts of weird bugs that no-one has seen
> >> before.
> >
> > Why do you have to do this? What are you doing that is so different
> > from everyone else? What drivers are you using that trigger this type
> > of thing?
> >
>
> This is all part of a larger patchset; I guess you weren't directly CCed.
> The name of the patchset is 'Introducing Device Tree Overlays' and is a
> method of changing the live device tree and have the changes reflected to
> the kernel's state.
Ok, no wonder I was confused :)
How about cc:ing me on the next round of these patches, all of the,
which will give me the proper background as to what is going on?
> >> In that case, the code path for creating platform devices from DT is
> >> not the same as the one that is used when creating platform device from
> >> a board file.
> >
> > Why not?
> >
>
> Because while DT creates platform devices, it doesn't use the platform device
> methods to do so, rather than builds the platform device itself. This is
> something that was overlooked.
Can't this be fixed? What does the platform device core need to do to
resolve this?
thanks,
greg k-h
next prev parent reply other threads:[~2013-01-18 2:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 22:31 [PATCH] platform: Fix platform device resource linking Pantelis Antoniou
2013-01-03 22:40 ` Greg Kroah-Hartman
2013-01-03 22:43 ` Pantelis Antoniou
2013-01-17 16:31 ` Greg Kroah-Hartman
2013-01-17 16:50 ` Pantelis Antoniou
2013-01-17 17:07 ` Greg Kroah-Hartman
2013-01-17 17:27 ` Pantelis Antoniou
2013-01-18 3:00 ` Greg Kroah-Hartman [this message]
2013-01-18 9:05 ` Pantelis Antoniou
2013-01-18 19:47 ` Greg Kroah-Hartman
2013-01-18 19:52 ` Pantelis Antoniou
2013-02-08 22:02 ` Grant Likely
2013-02-11 17:18 ` Pantelis Antoniou
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=20130118030017.GA11423@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Russ.Dill@ti.com \
--cc=koen@dominion.thruhere.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mporter@ti.com \
--cc=panto@antoniou-consulting.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 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.