From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from asavdk4.altibox.net ([109.247.116.15]:35140 "EHLO asavdk4.altibox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726017AbfFURvj (ORCPT ); Fri, 21 Jun 2019 13:51:39 -0400 Date: Fri, 21 Jun 2019 19:51:34 +0200 From: Sam Ravnborg Subject: Re: [PATCH] kbuild: compile-test global headers to ensure they are self-contained Message-ID: <20190621175134.GB16409@ravnborg.org> References: <20190621163931.19397-1-yamada.masahiro@socionext.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190621163931.19397-1-yamada.masahiro@socionext.com> Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Masahiro Yamada Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org, Michal Marek , linux-mediatek@lists.infradead.org, Matthias Brugger , linux-arm-kernel@lists.infradead.org Hi Masahiro. On Sat, Jun 22, 2019 at 01:39:31AM +0900, Masahiro Yamada wrote: > Make as many headers self-contained as possible so that they can be > included without relying on a specific include order. It is very nice finally to get some infrastructure to validate header files. But to avoid too many conflicts while including more and more headers that are selfcontained we really need something that is more distributed. So for example all header files in include/drm/* could be in one Makefile, incl. sub-directories, but the same Makefile would not include the files in include/soc/ If you just show how ot do it, others can follow-up with the relevant directories. Sam