linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	Alessandro Zummo <a.zummo@towertech.it>,
	rtc-linux@googlegroups.com, Shuah Khan <shuah.kh@samsung.com>
Subject: Re: mmotm 2013-06-05-17-24 uploaded (rtc)
Date: Thu, 6 Jun 2013 13:07:01 -0700	[thread overview]
Message-ID: <20130606130701.a17b25ed7cabde2fc9621800@linux-foundation.org> (raw)
In-Reply-To: <51B010B2.10309@infradead.org>

On Wed, 05 Jun 2013 21:31:46 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:

> On 06/05/13 17:26, akpm@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2013-06-05-17-24 has been uploaded to
> > 
> >    http://www.ozlabs.org/~akpm/mmotm/
> > 
> > mmotm-readme.txt says
> > 
> > README for mm-of-the-moment:
> > 
> > http://www.ozlabs.org/~akpm/mmotm/
> > 
> 
> on i386 when CONFIG_PM is not enabled:
> 
> drivers/rtc/class.c:339:18: error: lvalue required as unary '&' operand
> 
> due to:
> #define rtc_class_dev_pm_ops	NULL

hm, OK, thanks.  Shuah's "drivers/rtc/class: convert from Legacy pm ops
to dev_pm_ops" is busted and I'm not seeing a quick fix - the ifdeffery
in drivers/rtc/class.c is a bit odd (uses CONFIG_PM instead of
CONFIG_PM_SLEEP, for a start).  I'll drop it.

  reply	other threads:[~2013-06-06 20:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06  0:26 mmotm 2013-06-05-17-24 uploaded akpm
2013-06-06  2:04 ` Stephen Rothwell
2013-06-06  7:23   ` Geert Uytterhoeven
2013-06-06  7:37     ` Stephen Rothwell
2013-06-06  4:31 ` mmotm 2013-06-05-17-24 uploaded (rtc) Randy Dunlap
2013-06-06 20:07   ` Andrew Morton [this message]
2013-06-06  4:37 ` mmotm 2013-06-05-17-24 uploaded (ptp_pch) Randy Dunlap
2013-06-06 19:51   ` Ben Hutchings
2013-06-06 11:40 ` mmotm 2013-06-05-17-24 uploaded Robin Holt
2013-06-06 16:25 ` mmotm 2013-06-05-17-24 uploaded (sound/soc/codecs/adav80x) Randy Dunlap

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=20130606130701.a17b25ed7cabde2fc9621800@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=a.zummo@towertech.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rtc-linux@googlegroups.com \
    --cc=shuah.kh@samsung.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;
as well as URLs for NNTP newsgroup(s).