From: Brian Norris <computersforpeace@gmail.com>
To: Marek Vasut <marex@denx.de>
Cc: Stefan Roese <sr@denx.de>,
kbuild test robot <fengguang.wu@intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org, kbuild-all@01.org,
Graham Moore <grmoore@opensource.altera.com>
Subject: Re: [PATCH] mtd: spi-nor: don't build Cadence QuadSPI on non-ARM
Date: Tue, 19 Jul 2016 19:50:27 -0700 [thread overview]
Message-ID: <20160720025027.GA131957@google.com> (raw)
In-Reply-To: <3a769a42-f856-5b48-dd18-ef76a7bf4c91@denx.de>
On Wed, Jul 20, 2016 at 03:50:27AM +0200, Marek Vasut wrote:
> On 07/19/2016 10:05 PM, Brian Norris wrote:
> > On Tue, Jul 19, 2016 at 08:03:00AM +0200, Stefan Roese wrote:
> >> On 18.07.2016 22:20, Brian Norris wrote:
> >>> Hmm, does x86 not define readsl()/writesl()? I can never tell what
> >>> accessors are supposed to be "standard" across architectures.
> >>>
> >>> Either we need to drop the COMPILE_TEST or maybe make it (!X86 &&
> >>> COMPILE_TEST).
> >>
> >> iowrite32_rep() etc should work for x86 as well.
> >
> > Looks like it might. I'm not sure the original submitter can retest
> > right now (travel), so I'd probably rather just take the easy fix for
> > now, and we can widen to COMPILE_TEST later if desired.
>
> Isn't there a generic readsl() and writesl() implementation in
> include/asm-generic/io.h ?
Yes, but somehow x86 has managed to avoid that. I guess it's optional
for arch/<foo>/include/asm/io.h to include <asm-generic/io.h>? At any
rate, I double-checked myself by adding '#error "blah"' to
include/asm-generic/io.h, and x86 still seemed to build fine (at least
for the modules I was checking, like cadence-quadspi.o).
> > If I could get an ack on something like this, I'll apply it soon:
>
> This is fine, I am making a note to revisit this.
Cool. In that case...
> > ---8<---
> > From: Brian Norris <computersforpeace@gmail.com>
> > Date: Tue, 19 Jul 2016 13:02:40 -0700
> > Subject: [PATCH] mtd: spi-nor: don't build Cadence QuadSPI on non-ARM
> >
> > This controller driver is used only on ARM but is mostly written
> > portably so it can build on other arch'es. Unfortunately, at least x86
> > doesn't provibe readsl()/writesl() accessors. We could possibly fix this
> > issue in the future by using io{read,write}32_rep() instead, but let's
> > just drop the architectures we aren't using for now.
> >
> > Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Applied.
Brian
next prev parent reply other threads:[~2016-07-20 2:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 19:43 [mtd-next:master 30/33] drivers/mtd/spi-nor/cadence-quadspi.c:529:4: error: implicit declaration of function 'readsl' kbuild test robot
2016-07-18 20:20 ` Brian Norris
2016-07-19 6:03 ` Stefan Roese
2016-07-19 20:05 ` [PATCH] mtd: spi-nor: don't build Cadence QuadSPI on non-ARM Brian Norris
2016-07-20 1:50 ` Marek Vasut
2016-07-20 2:50 ` Brian Norris [this message]
2016-07-20 2:58 ` Marek Vasut
2016-07-20 3:25 ` Brian Norris
2016-07-20 5:59 ` Marek Vasut
2016-08-02 12:54 ` [mtd-next:master 30/33] drivers/mtd/spi-nor/cadence-quadspi.c:529:4: error: implicit declaration of function 'readsl' Marek Vasut
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=20160720025027.GA131957@google.com \
--to=computersforpeace@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=grmoore@opensource.altera.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=sr@denx.de \
--cc=x86@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).