[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20140220173456.8bf55b0ebf366ecad2e83047@canb.auug.org.au>
Date: Thu, 20 Feb 2014 17:34:56 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: akpm@...ux-foundation.org, mm-commits@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org, linux-next@...r.kernel.org,
Liam Girdwood <lgirdwood@...il.com>
Subject: Re: mmotm 2014-02-19-16-07 uploaded (sound/soc/intel/sst-dsp.c)
Hi Randy,
On Wed, 19 Feb 2014 21:41:36 -0800 Randy Dunlap <rdunlap@...radead.org> wrote:
>
> on i386:
> (from linux-next)
>
> CC sound/soc/intel/sst-dsp.o
> sound/soc/intel/sst-dsp.c: In function 'sst_dsp_outbox_write':
> sound/soc/intel/sst-dsp.c:218:2: error: implicit declaration of function 'memcpy_toio' [-Werror=implicit-function-declaration]
> sound/soc/intel/sst-dsp.c: In function 'sst_dsp_outbox_read':
> sound/soc/intel/sst-dsp.c:231:2: error: implicit declaration of function 'memcpy_fromio' [-Werror=implicit-function-declaration]
> cc1: some warnings being treated as errors
> make[4]: *** [sound/soc/intel/sst-dsp.o] Error 1
Which linux-next? How did you generate that error? I think I have that
driver disabled in linux-next ever since it was introduced due to getting
this error in one of my builds.
... thinks ...
I get it - the linux-next patch in Andrew's patch queue is based on the
part of linux-next *before* the commit that reverted the commit that
allowed that file to build. :-( Today, that will not happen. I'll see
if I can come up with a more permanent solution to that problem.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists