From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>,
moderated for non-subscribers <alsa-devel@alsa-project.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sanyog Kale <sanyog.r.kale@intel.com>
Subject: Re: [alsa-devel] linux-next: Tree for Oct 17 (soundwire)
Date: Thu, 17 Oct 2019 12:31:47 -0500 [thread overview]
Message-ID: <0f8fa7fb-dd1d-c26d-7756-a525aa46cf71@linux.intel.com> (raw)
In-Reply-To: <e8994e88-bdab-b3be-d62f-550ce9f2c76d@infradead.org>
On 10/17/19 10:22 AM, Randy Dunlap wrote:
> On 10/16/19 9:26 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20191016:
>>
>
> on x86_64:
>
> # CONFIG_BLOCK is not set
>
> CC [M] drivers/soundwire/intel_init.o
> In file included from ../drivers/soundwire/intel_init.c:12:0:
> ../include/linux/iomap.h: In function ‘iomap_sector’:
> ../include/linux/iomap.h:76:48: error: ‘SECTOR_SHIFT’ undeclared (first use in this function); did you mean ‘SECTIONS_SHIFT’?
> return (iomap->addr + pos - iomap->offset) >> SECTOR_SHIFT;
> ^~~~~~~~~~~~
> SECTIONS_SHIFT
Yes, looks like by fixing cross-compilation issues I added new ones.
We can either add an explicit dependency on CONFIG_BLOCK or remove the
use of ioread32() and use readl() instead. I didn't write the initial
code and I have no idea what the intent behind using ioread32 was.
prev parent reply other threads:[~2019-10-17 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 4:26 linux-next: Tree for Oct 17 Stephen Rothwell
2019-10-17 15:22 ` linux-next: Tree for Oct 17 (soundwire) Randy Dunlap
2019-10-17 17:31 ` Pierre-Louis Bossart [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=0f8fa7fb-dd1d-c26d-7756-a525aa46cf71@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sanyog.r.kale@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).