public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: paul@pwsan.com, linux-sh@vger.kernel.org, gregkh@suse.de,
	linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH 01/04] Driver Core: Add platform device arch data
Date: Fri, 29 May 2009 14:51:05 +0900	[thread overview]
Message-ID: <20090529055105.GD1122__11442.552021663$1243579391$gmane$org@linux-sh.org> (raw)
In-Reply-To: <aec7e5c30905282207v5fe17e6aj5a6382aa30d1774f@mail.gmail.com>

On Fri, May 29, 2009 at 02:07:35PM +0900, Magnus Damm wrote:
> 2009/5/29 Rafael J. Wysocki <rjw@sisk.pl>:
> > On Wednesday 27 May 2009, Magnus Damm wrote:
> >> --- 0001/arch/Kconfig
> >> +++ work/arch/Kconfig 2009-05-15 14:51:35.000000000 +0900
> >> @@ -112,3 +112,6 @@ config HAVE_DMA_API_DEBUG
> >>
> >> ?config HAVE_DEFAULT_NO_SPIN_MUTEXES
> >> ? ? ? bool
> >> +
> >> +config HAVE_PLATFORM_DEVICE_ARCHDATA
> >
> > Hmm. ?Do we really need yet another CONFIG_ option for that?
> 
> I don't think we need a total of 3 different config options for the
> platform device pm stuff, but I do think it makes sense to handle the
> platform archdata separately. Not sure which is the best way though,
> the #ifdefery is not very pretty. Maybe the best solution is just to
> drop the Kconfig stuff and add empty structures to all architecture
> versions of asm/device.h.
> 
A stub in asm-generic/device.h will cover the majority of cases. That is
much cleaner than adding to the Kconfig mess.

  parent reply	other threads:[~2009-05-29  5:51 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090527100625.29671.43166.sendpatchset@rx1.opensource.se>
2009-05-27 10:06 ` [PATCH 01/04] Driver Core: Add platform device arch data Magnus Damm
2009-05-27 10:06 ` [PATCH 02/04] Driver Core: Add idle and wakeup functions Magnus Damm
2009-05-27 10:06 ` [PATCH 03/04] PM: Add platform bus runtime dev_pm_ops Magnus Damm
2009-05-27 10:06 ` [PATCH 04/04] sh: Runtime platform device PM mockup Magnus Damm
2009-05-27 12:10 ` [PATCH 00/04][RFC] PM: Runtime platform device PM Mark Brown
2009-05-27 14:30 ` Alan Stern
2009-05-28  0:32 ` Kevin Hilman
     [not found] ` <20090527121042.GD1970@sirena.org.uk>
2009-05-28  6:02   ` Magnus Damm
     [not found] ` <Pine.LNX.4.44L0.0905271028050.2942-100000@iolanthe.rowland.org>
2009-05-28  6:14   ` Magnus Damm
     [not found]   ` <aec7e5c30905272314s54364f00u9bf5ecf48081dcda@mail.gmail.com>
2009-05-28  7:12     ` Rafael J. Wysocki
2009-05-28 15:33     ` Alan Stern
     [not found]     ` <Pine.LNX.4.44L0.0905281129090.3037-100000@iolanthe.rowland.org>
2009-05-29  7:41       ` Magnus Damm
2009-05-28 17:14 ` Kevin Hilman
     [not found] ` <20090527100633.29671.83531.sendpatchset@rx1.opensource.se>
2009-05-28 21:26   ` [PATCH 01/04] Driver Core: Add platform device arch data Rafael J. Wysocki
     [not found]   ` <200905282326.57431.rjw@sisk.pl>
2009-05-29  5:07     ` Magnus Damm
     [not found]     ` <aec7e5c30905282207v5fe17e6aj5a6382aa30d1774f@mail.gmail.com>
2009-05-29  5:51       ` Paul Mundt [this message]
     [not found] ` <20090527100642.29671.52231.sendpatchset@rx1.opensource.se>
2009-05-28 21:29   ` [PATCH 02/04] Driver Core: Add idle and wakeup functions Rafael J. Wysocki
     [not found]   ` <200905282329.09804.rjw@sisk.pl>
2009-05-29  5:10     ` Magnus Damm
     [not found]     ` <aec7e5c30905282210h23f0edc0vad4e29dd52c2e99c@mail.gmail.com>
2009-06-03  9:05       ` Rafael J. Wysocki
     [not found]       ` <200906031105.21977.rjw@sisk.pl>
2009-06-05  3:26         ` Magnus Damm
     [not found]         ` <aec7e5c30906042026u73f6d03dy9357a1527dabccc4@mail.gmail.com>
2009-06-05 20:42           ` Rafael J. Wysocki
     [not found]           ` <200906052242.08266.rjw@sisk.pl>
2009-06-09  4:22             ` Magnus Damm
     [not found]             ` <aec7e5c30906082122v456b3e31x367a20f8a46e1b37@mail.gmail.com>
2009-06-09 23:41               ` Rafael J. Wysocki
     [not found]               ` <200906100141.38833.rjw@sisk.pl>
2009-06-10  6:03                 ` Magnus Damm
     [not found]                 ` <aec7e5c30906092303k6d61279fl4bf55184e932a876@mail.gmail.com>
2009-06-10  8:19                   ` Rafael J. Wysocki
     [not found] ` <877i01p2t8.fsf@deeprootsystems.com>
2009-05-29  9:17   ` [PATCH 00/04][RFC] PM: Runtime platform device PM Magnus Damm
     [not found]   ` <aec7e5c30905290217s651e5785s2ceaebbe1856d120@mail.gmail.com>
2009-06-02 21:37     ` Pavel Machek
     [not found]     ` <20090602213722.GA1972@ucw.cz>
2009-06-04 10:03       ` Magnus Damm
     [not found] ` <20090527100650.29671.82139.sendpatchset@rx1.opensource.se>
2009-05-29 23:23   ` [PATCH 03/04] PM: Add platform bus runtime dev_pm_ops Rafael J. Wysocki
     [not found]   ` <200905300123.18367.rjw@sisk.pl>
2009-06-02 13:37     ` Magnus Damm
     [not found]     ` <aec7e5c30906020637i3fc67d10w23e21b035620798f@mail.gmail.com>
2009-06-03  9:47       ` Rafael J. Wysocki
2009-06-05 10:40         ` Magnus Damm
     [not found]         ` <aec7e5c30906050340x6b1cbb3bo6fe3aaddf4af5a56@mail.gmail.com>
2009-06-05 21:24           ` Rafael J. Wysocki

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='20090529055105.GD1122__11442.552021663$1243579391$gmane$org@linux-sh.org' \
    --to=lethal@linux-sh.org \
    --cc=gregkh@suse.de \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=paul@pwsan.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