From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: akpm@linux-foundation.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, linux-next@vger.kernel.org,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: mmotm 2014-02-19-16-07 uploaded (sound/soc/intel/sst-dsp.c)
Date: Thu, 20 Feb 2014 17:34:56 +1100 [thread overview]
Message-ID: <20140220173456.8bf55b0ebf366ecad2e83047@canb.auug.org.au> (raw)
In-Reply-To: <53059590.7040506@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
Hi Randy,
On Wed, 19 Feb 2014 21:41:36 -0800 Randy Dunlap <rdunlap@infradead.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@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-02-20 6:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 0:08 mmotm 2014-02-19-16-07 uploaded akpm
2014-02-20 5:41 ` mmotm 2014-02-19-16-07 uploaded (sound/soc/intel/sst-dsp.c) Randy Dunlap
2014-02-20 6:34 ` Stephen Rothwell [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=20140220173456.8bf55b0ebf366ecad2e83047@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=lgirdwood@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@infradead.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