public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM: mvebu: minor Armada 370 RD improvements
Date: Thu, 11 Sep 2014 10:26:01 -0400	[thread overview]
Message-ID: <20140911142601.GA30828@titan.lakedaemon.net> (raw)
In-Reply-To: <20140911160000.55a4de80@free-electrons.com>

+Ian

On Thu, Sep 11, 2014 at 04:00:00PM +0200, Thomas Petazzoni wrote:
> On Thu, 11 Sep 2014 15:43:23 +0200, Andrew Lunn wrote:
> > A point for discussion, triggered by 3/4. We have repeatedly seen
> > issues with modular builds, which we don't see with everything built
> > in. Can we improve our testing? Is there is way to take for example
> > mvebu_v7_defconfig and turn any y tristate options into m? Build and
> > boot? Get this added to the boot test farms?
> 
> I indeed agree that we are not testing much the modular case, but:
> 
>  1/ In my case, a mvebu_v7_defconfig where most the stuff would become
>     enabled as a module would make mvebu_v7_defconfig pretty much
>     useless for my daily work. When I'm doing active development, I
>     typically have everything built-in including the initramfs itself,
>     so that I don't rely on any storage/network to get the rootfs and
>     additional kernel drivers.
> 
>  2/ I don't think it would change much in terms of runtime coverage:
>     the tests done on the boot farm are just boot tests, I don't think
>     they load any kernel module. We could ask Kevin and Olof what
>     rootfs they use, but most likely it's some very small rootfs that
>     doesn't even have udev/mdev for automatic module loading. So no
>     module would be loaded, which would mean that a mvebu_v7_defconfig
>     with everything as a module would actually test *less* thing than a
>     configuration that has everything built in.
> 
> So, I agree on the observation, but I'm unsure the proposed solution
> will really solve or even improve the situation :/

Since debian does modular builds on a regular basis, maybe they have
some recommendations.

My thought is that I doubt we're the only SoC family with this issue.
To avoid the maintenance headache of extra _mod_defconfig's, perhaps we
could add a ./scripts/config toggle to turn the current .config enabled
tristates into modules?

thx,

Jason.

  reply	other threads:[~2014-09-11 14:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11  9:56 [PATCH 0/4] ARM: mvebu: minor Armada 370 RD improvements Thomas Petazzoni
2014-09-11  9:56 ` [PATCH 1/4] ARM: mvebu: add gpio fan support to Armada 370 RD Thomas Petazzoni
2014-09-11  9:56 ` [PATCH 2/4] ARM: mvebu: add user LED support of " Thomas Petazzoni
2014-09-11  9:56 ` [PATCH 3/4] ARM: mvebu: add LED class support built-in in mvebu_v7_defconfig Thomas Petazzoni
2014-09-11  9:56 ` [PATCH 4/4] ARM: mvebu: add gpio-fan to mvebu_v7_defconfig Thomas Petazzoni
2014-09-11 13:43 ` [PATCH 0/4] ARM: mvebu: minor Armada 370 RD improvements Andrew Lunn
2014-09-11 14:00   ` Thomas Petazzoni
2014-09-11 14:26     ` Jason Cooper [this message]
2014-09-11 14:26       ` Jason Cooper
2014-09-11 14:40         ` Andrew Lunn
2014-09-11 15:24         ` Ian Campbell
2014-09-13 21:27 ` Jason Cooper

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=20140911142601.GA30828@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.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