Re: dma-mapping commit breaks UML

From: Toralf FÃrster
Date: Wed Sep 29 2010 - 10:29:47 EST



FUJITA Tomonori wrote at 15:20:38
> On Wed, 29 Sep 2010 11:55:30 +0200
>
> Toralf **UNKNOWN CHARSET** <toralf.foerster@xxxxxx> wrote:
> > The
> >
> > 4565f0170dfc849b3629c27d769db800467baa62 is the first bad commit
> > commit 4565f0170dfc849b3629c27d769db800467baa62
> > Author: FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx>
> > 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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/