From: "Toralf Förster" <toralf.foerster@gmx.de>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: dma-mapping commit breaks UML
Date: Wed, 29 Sep 2010 16:29:38 +0200 [thread overview]
Message-ID: <201009291629.39077.toralf.foerster@gmx.de> (raw)
In-Reply-To: <20100929221620K.fujita.tomonori@lab.ntt.co.jp>
FUJITA Tomonori wrote at 15:20:38
> On Wed, 29 Sep 2010 11:55:30 +0200
>
> Toralf **UNKNOWN CHARSET** <toralf.foerster@gmx.de> wrote:
> > The
> >
> > 4565f0170dfc849b3629c27d769db800467baa62 is the first bad commit
> > commit 4565f0170dfc849b3629c27d769db800467baa62
> > Author: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> > Date: Tue Aug 10 18:03:22 2010 -0700
> >
> > dma-mapping: unify dma_get_cache_alignment implementations
>
> I think that the commit f3c072ad727617f00bffae17dba8cd895f5b7bdb
> already fixed this breakage. You still have the issue with the latest
> git?
Argh,
I use a script for git-bisect to catch this compile error in the current git kernel v2.6.36-rc6-20-g8189b14 :
...
CC arch/um/kernel/trap.o
arch/um/drivers/hostaudio_kern.c: In function ‘hostaudio_open’:
arch/um/drivers/hostaudio_kern.c:204: error: ‘__param_dsp’ undeclared (first use in this function)
arch/um/drivers/hostaudio_kern.c:204: error: (Each undeclared identifier is reported only once
arch/um/drivers/hostaudio_kern.c:204: error: for each function it appears in.)
arch/um/drivers/hostaudio_kern.c: In function ‘hostmixer_open_mixdev’:
arch/um/drivers/hostaudio_kern.c:265: error: ‘__param_mixer’ undeclared (first use in this function)
arch/um/drivers/hostaudio_kern.c:272: error: ‘__param_dsp’ undeclared (first use in this function)
make[1]: *** [arch/um/drivers/hostaudio_kern.o] Error 1
make: *** [arch/um/drivers] Error 2
make: *** Waiting for unfinished jobs....
...
but catched another compile error - how can I now automatically git-bisect for
that wrong commit w/o heavy scripting ? - Or simply asking who to blame wrt this compile error ?
--
MfG/Kind regards
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
next prev parent reply other threads:[~2010-09-29 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 9:55 dma-mapping commit breaks UML Toralf Förster
2010-09-29 13:20 ` FUJITA Tomonori
2010-09-29 14:29 ` Toralf Förster [this message]
2010-09-30 5:45 ` FUJITA Tomonori
2010-09-30 8:34 ` Toralf Förster
2010-09-30 8:34 ` Toralf Förster
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=201009291629.39077.toralf.foerster@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@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