ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: "Nikula, Jani" <jani.nikula@linux.intel.com>,
	Dave Airlie <airlied@linux.ie>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Grant Likely <grant.likely@linaro.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] (group) maintainership models
Date: Wed, 27 Jul 2016 09:53:24 +0200	[thread overview]
Message-ID: <17304523.rVA3ueAWN9@wuerfel> (raw)
In-Reply-To: <20160727030406.GU9681@localhost>

On Wednesday, July 27, 2016 8:34:06 AM CEST Vinod Koul wrote:
> > One thing we're low on for arm-soc is tooling, I know the x86 guys
> > have quite a bit more than we do in this area, so ideas on what we can
> > do to make our own lives easier is valuable.
> 
> Okay one of the gripes I have is that it is a bit hard to compile arm
> drivers. I regularly compile all drivers in subsystem I maintain and arm
> ones are not always straightforward. Figuring our which config to use
> for compile testing involves a bit of time, which I would like to avoid.
> 
> Having said that stuff like multi_xx_defconfig has improved a bit and
> seem to be in right direction (not an expert at arm arch's) but doesn't
> seem to cover all. Right now I am manually maintaining 4 different arm
> configs to compile test all the drivers in dmaengine subsystem which
> isn't a very big subsystem. For other arch's it is one config per
> subsystem.
> 
> So if you have suggestions to improve my flow, I would like to hear
> that, maybe I am doing something not right here...

We should be at the point where an 'allmodconfig' build on ARM
gets you most of the drivers and builds without warnings (using
gcc-4.9 or higher).

It will take a while to do the entire 'allmodconfig' build but
it's something that can be done as a background task.

One thing that we should still do is figure out which ARM specific
drivers are not included in allmodconfig and find a way to include
them too. Most platforms are compatible with a 'multiplatform'
setup (those that are not very rarely see patches at all and are
less likely to break), but allmodconfig will only include ARMv6
and ARMv7 based platforms, not ARMv4/ARMv4T/ARMv5. I've thought
about adding '|| COMPILE_TEST' dependencies to the platforms
with ARMv4/5 CPUs to have everything included in allmodconfig, but
I haven't actually tied that and I'm sure we'd see a lot of
build failures for correct code at first that we'd have to fix up
to make it work.

	Arnd

  parent reply	other threads:[~2016-07-27  7:53 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20 12:11 Daniel Vetter
2016-07-22 20:02 ` Darren Hart
2016-07-25  5:57   ` Daniel Vetter
2016-07-26 16:22     ` Darren Hart
2016-07-28 22:13       ` Bjorn Helgaas
2016-07-26 16:45 ` Olof Johansson
2016-07-27  3:04   ` Vinod Koul
2016-07-27  5:34     ` Wolfram Sang
2016-07-27  7:53     ` Arnd Bergmann [this message]
2016-07-27 12:57       ` Vinod Koul
2016-07-27 14:22         ` Mark Brown
2016-07-27 17:15           ` Vinod Koul
2016-07-28  8:44             ` Arnd Bergmann
2016-07-28 23:48               ` Alexandre Belloni
2016-07-29  0:06                 ` Stephen Rothwell
2016-07-31 17:57               ` Vinod Koul
2016-08-01  6:56                 ` Arnd Bergmann
2016-08-01  7:36                   ` Laurent Pinchart
2016-08-01 14:10                     ` Arnd Bergmann
2016-08-02  4:46                       ` Vinod Koul
2016-08-02  6:48                         ` Peter Ujfalusi
2016-08-02  7:27                           ` Arnd Bergmann
2016-08-02  8:29                             ` Peter Ujfalusi
2016-08-02  8:33                           ` Laurent Pinchart
2016-08-02  9:49                             ` Tony Lindgren
2016-08-02  8:41                           ` Russell King - ARM Linux
2016-08-02  9:21                             ` Laurent Pinchart
2016-08-02  9:27                               ` Russell King - ARM Linux
2016-09-02 10:46                   ` Vinod Koul
2016-09-02 17:25                     ` Linus Torvalds
2016-09-02 20:06                       ` Arnd Bergmann
2016-09-02 20:26                         ` Linus Torvalds
2016-09-02 20:43                           ` Julia Lawall
2016-09-02 20:50                             ` Linus Torvalds
2016-09-02 22:16                           ` Benjamin Herrenschmidt
2016-09-03 14:02                           ` Michael Ellerman
2016-09-02 23:35                         ` Arnd Bergmann
2016-09-04 17:45                       ` Geert Uytterhoeven
2016-09-04 17:59                         ` Linus Torvalds
2016-09-03  0:07                     ` Mark Brown
2016-07-27 12:59     ` Daniel Vetter
2016-07-27 13:03   ` Daniel Vetter
2016-08-01 14:42 ` Jani Nikula
2016-09-07  5:03 Leon Romanovsky

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=17304523.rVA3ueAWN9@wuerfel \
    --to=arnd@arndb.de \
    --cc=airlied@linux.ie \
    --cc=grant.likely@linaro.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=torvalds@linux-foundation.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox