From: Laurent Pinchart <email@example.com> To: Sam Ravnborg <firstname.lastname@example.org> Cc: email@example.com, Tomi Valkeinen <firstname.lastname@example.org>, Sascha Hauer <email@example.com>, Jyri Sarha <firstname.lastname@example.org>, Jonathan Hunter <email@example.com>, firstname.lastname@example.org, Thierry Reding <email@example.com>, firstname.lastname@example.org, Laurentiu Palcu <email@example.com>, firstname.lastname@example.org, Shawn Guo <email@example.com> Subject: Re: [PATCH 0/7] drm: Extend COMPILE_TEST support to some ARM drivers Date: Fri, 30 Jul 2021 22:33:19 +0300 [thread overview] Message-ID: <YQRT/9xIH2PyACbt@pendragon.ideasonboard.com> (raw) In-Reply-To: <YQLdDTu4duXXQXAs@ravnborg.org> Hi Sam, On Thu, Jul 29, 2021 at 06:53:33PM +0200, Sam Ravnborg wrote: > On Wed, Jul 28, 2021 at 06:37:29PM +0300, Laurent Pinchart wrote: > > Hello, > > > > This patch series stems from subsystem-wide changes I wanted to > > compile-test with an ARM64 cross-compiler. My laziness to fire a 32-bit > > ARM build probably resulted in more time being spent writing these > > patches, but hopefully they'll turn out to be useful for more people :-) > > > > Patches 1/7 and 2/7 are fixes for compilation warnings on 64-bit > > platforms in the omapdrm and sti-drm drivers. They are a dependency for > > the Kconfig changes that follow to avoid introducing build warnings, but > > could also be merged before. > > > > Patches 3/7 to 7/7 enable compilation of the imx-dcss, omapdrm, sti-drm, > > tegra-drm and tilcdc drivers on ARM64 with COMPILE_TEST. The patches are > > independent from each other, so they can be picked by their respective > > maintainers. > > > > We could also extend test compilation to more architecture, but I didn't > > want to remove all dependencies on ARM or ARM64 at this point for fear > > or triggering build warnings that I wouldn't be able to catch locally. > > If there's a consensus that fully relaxing the platform requirement is > > better, I can submit a new version that does so and rely on the 0day bot > > to catch issues. > > I have alpha, sparc64, and a few more so we can get pretty good coverage > before it hits -next. It seems that the consensus is to enable COMPILE_TEST on all platforms, so I'll do that. > If we enable more build coverage then please address all W=1 warnings > first. > > I for once always builds with W=1 these days, and I see more and more > warnings sneaking in again. > So lets try to keep the noise level down. Hmmmm... I build my kernel with -Werror to make sure I catch all warnings. W=1 doesn't play well with that :-S I'll see if I can turn the additional warnings into non-errors, but that may become a game of whack-a-mole. -- Regards, Laurent Pinchart
prev parent reply other threads:[~2021-07-30 19:33 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-28 15:37 Laurent Pinchart 2021-07-28 15:37 ` [PATCH 1/7] drm/omap: Cast pointer to integer safely Laurent Pinchart 2021-07-29 6:13 ` Tomi Valkeinen 2021-07-31 0:25 ` Laurent Pinchart 2021-07-28 15:37 ` [PATCH 2/7] drm/sti: Use correct printk format specifiers for size_t Laurent Pinchart 2021-07-30 9:35 ` Philippe CORNU 2021-07-28 15:37 ` [PATCH 3/7] drm/imx/dcss: Enable COMPILE_TEST on all ARM64 platforms Laurent Pinchart 2021-07-30 12:10 ` Geert Uytterhoeven 2021-07-30 12:31 ` Philipp Zabel 2021-07-28 15:37 ` [PATCH 4/7] drm/omap: Enable COMPILE_TEST on all ARM and " Laurent Pinchart 2021-07-28 15:37 ` [PATCH 5/7] drm/sti: " Laurent Pinchart 2021-07-30 9:39 ` Philippe CORNU 2021-07-28 15:37 ` [PATCH 6/7] drm/tegra: Enable COMPILE_TEST on all " Laurent Pinchart 2021-07-28 15:37 ` [PATCH 7/7] drm/tilcdc: " Laurent Pinchart 2021-07-29 6:19 ` [PATCH 0/7] drm: Extend COMPILE_TEST support to some ARM drivers Tomi Valkeinen [not found] ` <YQLdDTu4duXXQXAs@ravnborg.org> 2021-07-30 19:33 ` Laurent Pinchart [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=YQRT/9xIH2PyACbt@pendragon.ideasonboard.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 0/7] drm: Extend COMPILE_TEST support to some ARM drivers' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).