From: Randy Dunlap <randy.dunlap@oracle.com>
To: "werner" <w.landgraf@ru.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.37-rc1 problems
Date: Mon, 1 Nov 2010 15:26:24 -0700 [thread overview]
Message-ID: <20101101152624.f567dbe2.randy.dunlap@oracle.com> (raw)
In-Reply-To: <web-395637137@zbackend1.aha.ru>
On Mon, 01 Nov 2010 18:14:12 -0400 werner wrote:
> 2.6.37-rc1 probelms:
>
> ===========================
>
> CC [M]
> drivers/staging/ath6kl/hif/sdio/linux_sdio/src/hif_scatter.o
> drivers/staging/ath6kl/hif/sdio/linux_sdio/src/hif_scatter.c:
> In function 'SetupHIFScatterSupport':
> drivers/staging/ath6kl/hif/sdio/linux_sdio/src/hif_scatter.c:288:
> error: 'struct mmc_host' has no member named 'max_hw_segs'
> drivers/staging/ath6kl/hif/sdio/linux_sdio/src/hif_scatter.c:289:
> error: 'struct mmc_host' has no member named 'max_hw_segs'
Already reported, Greg said that he would fix it up.
> make[3]:
> [drivers/staging/ath6kl/hif/sdio/linux_sdio/src/hif_scatter.o]
> Error 1 (ignored)
> LD [M] drivers/staging/ath6kl/ath6kl.o
> ld:
> drivers/staging/ath6kl/hif/sdio/linux_sdio/src/hif_scatter.o:
> No such file: No such file or directory
Comes from error above and using -i or -k (as I do).
> make[3]: [drivers/staging/ath6kl/ath6kl.o] Error 1
> (ignored)
>
> ============================
>
> CC [M] drivers/staging/solo6x10/solo6010-core.o
> CC [M] drivers/staging/solo6x10/solo6010-i2c.o
> CC [M] drivers/staging/solo6x10/solo6010-p2m.o
> CC [M] drivers/staging/solo6x10/solo6010-v4l2.o
> drivers/staging/solo6x10/solo6010-v4l2.c: In function
> 'solo_v4l2_open':
> drivers/staging/solo6x10/solo6010-v4l2.c:440: error: too
> few arguments to function 'videobuf_queue_dma_contig_init'
> make[3]: [drivers/staging/solo6x10/solo6010-v4l2.o] Error
> 1 (ignored)
> CC [M] drivers/staging/solo6x10/solo6010-tw28.o
> CC [M] drivers/staging/solo6x10/solo6010-gpio.o
> CC [M] drivers/staging/solo6x10/solo6010-disp.o
> CC [M] drivers/staging/solo6x10/solo6010-enc.o
> CC [M] drivers/staging/solo6x10/solo6010-v4l2-enc.o
> drivers/staging/solo6x10/solo6010-v4l2-enc.c: In function
> 'solo_enc_open':
> drivers/staging/solo6x10/solo6010-v4l2-enc.c:769: error:
> too few arguments to function
> 'videobuf_queue_dma_contig_init'
> make[3]: [drivers/staging/solo6x10/solo6010-v4l2-enc.o]
> Error 1 (ignored)
> CC [M] drivers/staging/solo6x10/solo6010-g723.o
> LD [M] drivers/staging/solo6x10/solo6x10.o
> ld: drivers/staging/solo6x10/solo6010-v4l2.o: No such
> file: No such file or directory
> make[3]: [drivers/staging/solo6x10/solo6x10.o] Error 1
> (ignored)
>
> ===============================
>
> CC [M] fs/logfs/compr.o
> In file included from fs/logfs/compr.c:8:
[snip huge list of messages]
Fixed by today's commit:
commit e99d11d19977c74b18411cdb59cdebb788237a6e
Author: Paul Mundt <lethal@linux-sh.org>
Date: Tue Nov 2 05:29:21 2010 +0900
fs: logfs: Fix up MTD=y build.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2010-11-01 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 22:14 2.6.37-rc1 problems werner
2010-11-01 22:26 ` Randy Dunlap [this message]
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=20101101152624.f567dbe2.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=w.landgraf@ru.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.