From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423120AbcFML7d (ORCPT ); Mon, 13 Jun 2016 07:59:33 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:34220 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1422954AbcFML7c (ORCPT ); Mon, 13 Jun 2016 07:59:32 -0400 Date: Mon, 13 Jun 2016 12:59:11 +0100 From: Mark Brown To: Sudip Mukherjee Cc: Andrew Morton , linux-kernel@vger.kernel.org, Simran Rai , Christoph Hellwig Message-ID: <20160613115911.GG2282@sirena.org.uk> References: <1465763104-6227-1-git-send-email-sudipm.mukherjee@gmail.com> <20160612213224.fcjalhwmjqwpjhui@rhwork> <20160613074112.GA2031@sudip-tp> <20160613092934.GE2282@sirena.org.uk> <20160613105108.GA5926@sudip-tp> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="yHmUJ2Jgby4Rx//r" Content-Disposition: inline In-Reply-To: <20160613105108.GA5926@sudip-tp> X-Cookie: Your present plans will be successful. User-Agent: Mutt/1.6.0 (2016-04-01) X-SA-Exim-Connect-IP: 81.128.185.34 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH] dma: remove bad_dma_ops to fix build fail X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --yHmUJ2Jgby4Rx//r Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jun 13, 2016 at 11:51:08AM +0100, Sudip Mukherjee wrote: > On Mon, Jun 13, 2016 at 10:29:34AM +0100, Mark Brown wrote: > > Right, we've got a couple of obscure architectures with no DMA support > > which are leading to a constant stream of patches like this that are > > being triggered by compile coverage stuff. In situations like this we > > very often provide stubs rather than having to handle this in lots of > > different places in the code. > Ok, I will do that. But I am seeing arch/m32r/include/asm/m32102.h is > defining the DMA Controller registers and also a MAX_DMA_ADDRESS is > defined in dma.h. Doesn't that mean that this arch is capable of DMA? Quite possibly, but they don't seem to implement the standard interfaces for generic code (this sort of thing is quite common for the less widely used architectures sadly). --yHmUJ2Jgby4Rx//r Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXXqALAAoJECTWi3JdVIfQge8H/1Rg8yD9eXw4zZIXrnrRd8OM H3B/S2ynvJb70JkgikdCJWoDS6VdYlEeETHOaJFuO9vVDRiKis8UNCj/zhsmuVK+ X6QM69vxNRm4GSiPD+ce2kbvOeKXjG7UIjzuOz3A1T4mJLAEzfPm6kt2BqExT32m jdTLn3b27m7UVp13MbrOajPw9jldrsf4x8QGnN12OLlQIll2GMl8ZHJ64b4yNNBu D6OrqTWYFAYpa0Fl0w6sIbLgSH4a/G0XB8U5VAjP8drTXKRrI4KJUBR5oHdYtpYc 61VU+I2m6AU+eOocfkxz2DbnmkAG+QFiSDzQrFN5vTGUOFBxTPhb7L//WJzEO8s= =1SBd -----END PGP SIGNATURE----- --yHmUJ2Jgby4Rx//r--