From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pierre Ossman <drzeus-mmc@drzeus.cx>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Philip Langdale <philipl@overt.org>, Greg KH <greg@kroah.com>
Subject: Re: mmotm 2008-12-30-16-05 uploaded (mmc)
Date: Wed, 31 Dec 2008 19:48:31 +0100 [thread overview]
Message-ID: <200812311948.31697.rjw@sisk.pl> (raw)
In-Reply-To: <20081231190747.3416280d@mjolnir.drzeus.cx>
On Wednesday 31 December 2008, Pierre Ossman wrote:
> On Tue, 30 Dec 2008 19:59:01 -0800
> Randy Dunlap <randy.dunlap@oracle.com> wrote:
>
> > akpm@linux-foundation.org wrote:
> > > The mm-of-the-moment snapshot 2008-12-30-16-05 has been uploaded to
> > >
> > > http://userweb.kernel.org/~akpm/mmotm/
> > >
> > > and will soon be available at
> > >
> > > git://git.zen-sources.org/zen/mmotm.git
> > >
> > > It contains the following patches against 2.6.28:
> >
> >
> > mmotm-2008-1230-1605/drivers/mmc/host/ricoh_mmc.c:235: error: variable 'ricoh_mmc_pm_opts' has initializer but incomplete type
> > mmotm-2008-1230-1605/drivers/mmc/host/ricoh_mmc.c:236: error: unknown field 'suspend_noirq' specified in initializer
> > mmotm-2008-1230-1605/drivers/mmc/host/ricoh_mmc.c:236: warning: excess elements in struct initializer
> > mmotm-2008-1230-1605/drivers/mmc/host/ricoh_mmc.c:236: warning: (near initialization for 'ricoh_mmc_pm_opts')
> > mmotm-2008-1230-1605/drivers/mmc/host/ricoh_mmc.c:237: error: unknown field 'resume_noirq' specified in initializer
> > mmotm-2008-1230-1605/drivers/mmc/host/ricoh_mmc.c:237: warning: excess elements in struct initializer
> > mmotm-2008-1230-1605/drivers/mmc/host/ricoh_mmc.c:237: warning: (near initialization for 'ricoh_mmc_pm_opts')
> >
> >
> > struct dev_pm_ops seems not to exist AFAICT.
> >
> >
>
> This is no longer in my tree so it must be some bad ordering in
> Rafael's tree.
That's because the Greg's driver core tree has been dropped temporarily
due to a build error.
Thanks,
Rafael
next prev parent reply other threads:[~2008-12-31 18:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200812310006.mBV060iV029753@imap1.linux-foundation.org>
2008-12-31 3:51 ` mmotm 2008-12-30-16-05 uploaded (mtd) Randy Dunlap
2008-12-31 3:59 ` mmotm 2008-12-30-16-05 uploaded (mmc) Randy Dunlap
2008-12-31 18:07 ` Pierre Ossman
2008-12-31 18:48 ` Rafael J. Wysocki [this message]
2008-12-31 4:07 ` [PATCH mmotm] input: fix function arg list Randy Dunlap
2008-12-31 4:21 ` [PATCH] spi.h uses/needs device.h Randy Dunlap
2009-01-01 21:58 ` Guennadi Liakhovetski
2008-12-31 6:26 ` [PATCH mmotm] leds-dac124s085: use header files for interfaces Randy Dunlap
2008-12-31 14:42 ` [PATCH for mmotm1230] acpi: fix unused variable warnings KOSAKI Motohiro
2008-12-31 14:45 ` [PATCH for mmotm1230] input: fix incomplete prototype of input_init_abs_bypass() KOSAKI Motohiro
2009-01-01 1:51 ` [mmotm 2008-12-30-16-05] Warning at MPT driver initialization Tetsuo Handa
2009-01-01 2:26 ` Andrew Morton
2009-01-05 16:45 ` Eric Paris
2009-01-12 22:19 ` Andrew Morton
2009-01-01 20:51 ` mmotm 2008-12-30-16-05 uploaded Valdis.Kletnieks
2009-01-02 2:31 ` Andrew Morton
2009-01-02 2:42 ` Valdis.Kletnieks
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=200812311948.31697.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=drzeus-mmc@drzeus.cx \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philipl@overt.org \
--cc=randy.dunlap@oracle.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
Powered by JetHome