[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130120234005.GA14196@kroah.com>
Date: Sun, 20 Jan 2013 15:40:05 -0800
From: Greg KH <gregkh@...uxfoundation.org>
To: Jon Mason <jon.mason@...el.com>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
Dave Jiang <dave.jiang@...el.com>,
Nicholas Bellinger <nab@...ux-iscsi.org>
Subject: Re: [PATCH 01/21] NTB: correct missing readq/writeq errors
On Sat, Jan 19, 2013 at 02:02:15AM -0700, Jon Mason wrote:
> Atomic readq and writeq do not exist by default on some 32bit
> architectures, thus causing compile errors due to non-existent symbols.
> In those cases, use the definitions of those symbols from
> include/asm-generic/io-64-nonatomic-hi-lo.h
>
> Signed-off-by: Jon Mason <jon.mason@...el.com>
> ---
> drivers/ntb/ntb_hw.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/ntb/ntb_hw.c b/drivers/ntb/ntb_hw.c
> index 4c71b17..0b46fef 100644
> --- a/drivers/ntb/ntb_hw.c
> +++ b/drivers/ntb/ntb_hw.c
> @@ -45,6 +45,7 @@
> * Contact Information:
> * Jon Mason <jon.mason@...el.com>
> */
> +#include <asm-generic/io-64-nonatomic-hi-lo.h>
Really? This seems really odd. Usually we just don't build the code
for any platform that doesn't have readq/writeq. Otherwise, shouldn't
those arches just include this file themselves to keep everything
working? Individual drivers shouldn't have to do this.
So, I'm not going to take this one just yet, sorry.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists