From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Ball <cjb@laptop.org>
Subject: Fix for mmc/core.h completion [was Re: linux-next: triage for March 14, 2012]
Date: Fri, 16 Mar 2012 10:46:18 -0400 [thread overview]
Message-ID: <4F63523A.8090804@windriver.com> (raw)
In-Reply-To: <CAMuHMdV45SBg+cm0+x07SfvY-xpjqb_ZVznn-vD=70G1YZXnFw@mail.gmail.com>
On 12-03-15 04:00 AM, Geert Uytterhoeven wrote:
> On Thu, Mar 15, 2012 at 00:39, Paul Gortmaker
> <paul.gortmaker@windriver.com> wrote:
>> New breakage since last report:
>
> Seems you missed two new failures for m68k/allmodconfig:
>
> include/linux/mmc/core.h:128:20: error: field 'completion' has incomplete type
> make[4]: *** [drivers/mmc/card/mmc_test.o] Error 1
The above I've fixed up. The file obviously needed completion.h but
curious that it only showed up now. I'm guessing it was masked by
the other errors happening earlier and blocking a full build, since
the device cleanup has been in linux-next for a while.
I've amended this commit in my device-3.4 cleanup tree to add it.
---------
commit 6adab8a8e42d1da155a0ec0c716fa2573e61b0e5
Author: Paul Gortmaker <paul.gortmaker@windriver.com>
Date: Mon Jan 30 11:46:54 2012 -0500
device.h: audit and cleanup users in main include dir
---------
[Added Chris to CC so he knows he doesn't need to worry about this]
Thanks,
Paul.
>
> drivers/staging/android/persistent_ram.c:457:2: error: implicit
> declaration of function 'memblock_reserve'
> [-Werror=implicit-function-declaration]
> cc1: some warnings being treated as errors
> make[4]: *** [drivers/staging/android/persistent_ram.o] Error 1
>
>> m68k:allmodconfig
>> when: Mar 9, 00:38
>> why: ERROR: "__udivdi3" [drivers/media/dvb/frontends/rtl2830.ko] undefined!
>
> This seems to be fixed, unless it doesn't get that far anymore.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
next prev parent reply other threads:[~2012-03-16 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 23:39 linux-next: triage for March 14, 2012 Paul Gortmaker
2012-03-15 8:00 ` Geert Uytterhoeven
2012-03-15 14:34 ` Paul Gortmaker
2012-03-16 14:46 ` Paul Gortmaker [this message]
2012-03-21 8:33 ` Geert Uytterhoeven
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=4F63523A.8090804@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=cjb@laptop.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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