Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755668AbcLSLFl (ORCPT ); Mon, 19 Dec 2016 06:05:41 -0500 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:46332 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753656AbcLSLFh (ORCPT ); Mon, 19 Dec 2016 06:05:37 -0500 Date: Mon, 19 Dec 2016 11:04:04 +0000 From: Mark Brown To: Darren Hart Cc: Andy Shevchenko , Pierre-Louis Bossart , Irina Tirdea , linux-clk@vger.kernel.org, "x86@kernel.org" , platform-driver-x86@vger.kernel.org, Stephen Boyd , Thomas Gleixner , Michael Turquette , Ingo Molnar , "H. Peter Anvin" , ALSA Development Mailing List , Takashi Iwai , Pierre-Louis Bossart , "Rafael J. Wysocki" , Len Brown , "linux-acpi@vger.kernel.org" , "linux-kernel@vger.kernel.org" Message-ID: <20161219110404.cnk43zqenn2m7ib2@sirena.org.uk> References: <1481306510-7471-1-git-send-email-irina.tirdea@intel.com> <1481306510-7471-2-git-send-email-irina.tirdea@intel.com> <1a98dcda-a662-958e-307f-5fe3f281ed9f@linux.intel.com> <20161216183607.GB44199@f23x64.localdomain> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="exmomhpvdqifvrc4" Content-Disposition: inline In-Reply-To: <20161216183607.GB44199@f23x64.localdomain> X-Cookie: I represent a sardine!! User-Agent: NeoMutt/20161126 (1.7.1) X-SA-Exim-Connect-IP: 2001:470:1f1d:6b5::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH v6 1/3] clk: x86: Add Atom PMC platform clocks X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: No (on mezzanine.sirena.org.uk); Unknown failure Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1303 Lines: 33 --exmomhpvdqifvrc4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Dec 16, 2016 at 10:36:07AM -0800, Darren Hart wrote: > My understanding is include/linux should be more generic, rather than platform > specific headers. So while platform_data may refer specifically to the platform > bus drivers, it's the closest thing we have to include/platform, which would be > ideal. I would prefer to stick with include/platform_data because: It's not specific to the platform bus, it's for use with the platform_data pointer embedded in struct device that all buses can have - it's extensively used for things like I2C and SPI for example. But really it doesn't matter *that* much. --exmomhpvdqifvrc4 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAlhXvqAACgkQJNaLcl1U h9BxzQf/c8nqU+66S2miVJyYdJbh8d9Ed+afKoeeTozs1u6KcCMaigFS1hyUKSk1 ZKyGQy32B5iSGauGTYwbRJnz39qUg2d4Jay9XK8IEZoZLw/IiZ90CaXFkvtX2YVn 61P9OcYJE3eq57I6i8dhLD7bR9uI9CxIXS8fRbf7RaZd1wRb/z4s6z7YMFVJYvIS zkzw0KrmIb+4AQfvWFuXw51xujERcnfBHnjHq1JX/yxqihmSJYg4/wi3pgNdKjEl 4AQc+r37wMLWO1LU7XP6H7TRKagVzriXtyap9zi/YtHoewnyrKkzVjcJMduOaEmf OVSJefChGjkkQUUcAgaG/SVwRJH+RA== =CT+F -----END PGP SIGNATURE----- --exmomhpvdqifvrc4--