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: Fri, 18 Jan 2013 11:47:17 -0800 [thread overview]
Message-ID: <20130118194717.GB18658@kroah.com> (raw)
In-Reply-To: <82FE4A4D-DCA8-4C2C-97E7-6B73D424DCF5@antoniou-consulting.com>
On Fri, Jan 18, 2013 at 11:05:14AM +0200, Pantelis Antoniou wrote:
> It might make sense for the of_device_* functions that are duplicating
> platform_device_* functions to be removed, and their functionality to
> be subsumed by platform_device_*, possibly by calling some helper functions
> in drivers/of/ when of_node is not NULL. The of_device_* functions can be
> replaced by a direct call to platform_device_* via a define (until all of
> the callers get converted).
That sounds reasonable.
> The problem with doing anything like this would be that a whole bunch of
> devices/arches depend on DT, and if anything breaks there will be a lot of
> angry people with pitchforks after the culprit.
That's nothing new, we are totally used to that happening :)
> So without the full force of a core maintainer behind such a move, people
> are reluctant to do so.
Send patches if you want to do this, no need for the maintainer to do it
(hint, I will not as I don't even have a system that this type of code
runs on.)
thanks,
greg k-h
next prev parent reply other threads:[~2013-01-18 19:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 22:31 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
2013-01-18 9:05 ` Pantelis Antoniou
2013-01-18 19:47 ` Greg Kroah-Hartman [this message]
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=20130118194717.GB18658@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®