Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752954AbaDQQHh (ORCPT ); Thu, 17 Apr 2014 12:07:37 -0400 Received: from mail-la0-f47.google.com ([209.85.215.47]:61720 "EHLO mail-la0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751006AbaDQQHa (ORCPT ); Thu, 17 Apr 2014 12:07:30 -0400 MIME-Version: 1.0 In-Reply-To: <1397742261-15621-11-git-send-email-will.deacon@arm.com> References: <1397742261-15621-1-git-send-email-will.deacon@arm.com> <1397742261-15621-11-git-send-email-will.deacon@arm.com> Date: Thu, 17 Apr 2014 18:07:28 +0200 X-Google-Sender-Auth: Ft1ODpA_oRVTm_g3pxSzCmL-xNs Message-ID: Subject: Re: [PATCH 10/18] m68k: io: implement dummy relaxed accessor macros for writes From: Geert Uytterhoeven To: Will Deacon Cc: Linux-Arch , "linux-kernel@vger.kernel.org" , Arnd Bergmann , Michal Simek , David Howells , Mark Brown , Benjamin Herrenschmidt , Peter Zijlstra , Paul McKenney Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 17, 2014 at 3:44 PM, Will Deacon wrote: > write{b,w,l}_relaxed are implemented by some architectures in order to > permit memory-mapped I/O accesses with weaker barrier semantics than the > non-relaxed variants. > > This patch adds dummy macros for the write accessors to m68k, in the > same vein as the dummy definitions for the relaxed read accessors. > Additionally, the existing relaxed read accessors are moved into > asm/io.h, so that they can be used by m68k targets with an MMU. > > Cc: Geert Uytterhoeven > Signed-off-by: Will Deacon Acked-by: Geert Uytterhoeven Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/