From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ale.deltatee.com (ale.deltatee.com. [207.54.116.67]) by gmr-mx.google.com with ESMTPS id u66si33603itd.1.2017.08.04.08.47.47 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 04 Aug 2017 08:47:47 -0700 (PDT) References: <20170803183018.5889-1-logang@deltatee.com> <20170803183018.5889-2-logang@deltatee.com> <2b41b02c-07e3-b927-f276-a29480f94285@ti.com> From: Logan Gunthorpe Message-ID: <15c19bbe-a178-5c60-530e-14229bfdc906@deltatee.com> Date: Fri, 4 Aug 2017 09:47:37 -0600 MIME-Version: 1.0 In-Reply-To: <2b41b02c-07e3-b927-f276-a29480f94285@ti.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [PATCH v6 1/7] drm/tilcdc: ensure nonatomic iowrite64 is not used To: Tomi Valkeinen , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, linux-ntb@googlegroups.com, linux-crypto@vger.kernel.org, Jyri Sarha Cc: Arnd Bergmann , Greg Kroah-Hartman , Andy Shevchenko , =?UTF-8?Q?Horia_Geant=c4=83?= , Stephen Bates , David Airlie List-ID: On 04/08/17 07:03 AM, Tomi Valkeinen wrote: > I haven't really followed the discussion on this, but if the tilcdc's > use of iowrite64 causes (real) problems/complications elsewhere, I think > we could drop it. Well, that's up to you. The patch I submitted should still be correct though, and if arm ever gets a proper atomic iowrite64 implementation it would be good to use it. So in an annotative sense it's nice to keep the function call in there. Thanks, Logan