linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Jim Davis <jim.epost@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next <linux-next@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	perex <perex@perex.cz>,
	tiwai@suse.de, lgirdwood@gmail.com, broonie <broonie@kernel.org>
Subject: Re: randconfig build error with next-20140226, in sound/soc/intel/sst-baytrail-ipc.c
Date: Wed, 26 Feb 2014 16:48:04 +0200	[thread overview]
Message-ID: <530DFEA4.70601@linux.intel.com> (raw)
In-Reply-To: <CA+r1Zhhs8=Vu5uDVoAbyP0JRsRscwhdQ8Dns6cTaABS9Duj8dw@mail.gmail.com>

On 02/26/2014 04:36 PM, Jim Davis wrote:
> Building with the attached random configuration file,
>
> sound/soc/intel/sst-baytrail-ipc.c: In function 'sst_byt_get_dsp_position':
> sound/soc/intel/sst-baytrail-ipc.c:743:2: error: implicit declaration
> of function 'memcpy_fromio' [-Werror=implicit-function-declaration]
>    memcpy_fromio(&fw_tstamp,
>    ^
> cc1: some warnings being treated as errors
> make[3]: *** [sound/soc/intel/sst-baytrail-ipc.o] Error 1
Thanks, I posted a fix for it earlier today:

http://mailman.alsa-project.org/pipermail/alsa-devel/2014-February/073299.html

Fix is not yet committed so I guess we can have your reported by too?

Reported-by: Jim Davis <jim.epost@gmail.com>

-- 
Jarkko

      reply	other threads:[~2014-02-26 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 14:36 randconfig build error with next-20140226, in sound/soc/intel/sst-baytrail-ipc.c Jim Davis
2014-02-26 14:48 ` Jarkko Nikula [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=530DFEA4.70601@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=jim.epost@gmail.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=sfr@canb.auug.org.au \
    --cc=tiwai@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).