netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
	linux-can@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2] net: can: Disable flexcan driver build for big endian CPU on ARM
Date: Mon, 06 Jan 2014 14:23:16 +0100	[thread overview]
Message-ID: <52CAAE44.1020100@pengutronix.de> (raw)
In-Reply-To: <1389014463-14649-1-git-send-email-linux@roeck-us.net>

[-- Attachment #1: Type: text/plain, Size: 810 bytes --]

On 01/06/2014 02:21 PM, Guenter Roeck wrote:
> Building arm:allmodconfig fails with
> 
> flexcan.c: In function 'flexcan_read':
> flexcan.c:243:2: error: implicit declaration of function 'in_be32'
> flexcan.c: In function 'flexcan_write':
> flexcan.c:248:2: error: implicit declaration of function 'out_be32'
> 
> in_be32 and out_be32 do not (or no longer) exist for ARM targets.
> Disable the build for ARM on big endian CPUs.
> 
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>

Applied to can-next.

Tnx,
Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2014-01-06 13:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 13:21 [PATCH v2] net: can: Disable flexcan driver build for big endian CPU on ARM Guenter Roeck
2014-01-06 13:23 ` Marc Kleine-Budde [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-14 10:44 Arnd Bergmann
2014-01-16 16:49 ` Marc Kleine-Budde

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=52CAAE44.1020100@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=netdev@vger.kernel.org \
    --cc=wg@grandegger.com \
    /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).