From: Lee Jones <lee.jones@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
Pawel Moll <pawel.moll@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: vexpress: refine dependencies for new code
Date: Tue, 27 May 2014 10:18:36 +0100 [thread overview]
Message-ID: <20140527091836.GE5875@lee--X1> (raw)
In-Reply-To: <6862654.ZzBrnrRESe@wuerfel>
> The versatile express changes for 3.16 introduced a number of
> build regressions for randconfig kernels by not tracking dependencies
> between the components right.
>
> This patch tries to rectify that:
>
> * the mach-vexpress code cannot link without the syscfg driver,
> which in turn needs MFD_VEXPRESS_SYSREG
> * various drivers call devm_regmap_init_vexpress_config(), which
> has to be exported so it can be used by loadable modules
> * the configuration bus uses OF DT helper functions that are not
> available to platforms disable CONFIG_OF
> * The sysreg driver exports GPIOs through gpiolib, which can
> be disabled on some platforms.
> * The clocksource code cannot be built on platforms that don't
> use modern timekeeping but rely on gettimeoffset.
Where's the diff?
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
[...]
> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
For the MFD part:
Acked-by: Lee Jones <lee.jones@linaro.org>
This patch has a high chance of creating conflicts. Can someone apply
this to a branch, tag it and sent out a pull-request to the other
maintainers please?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2014-05-27 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 15:34 [PATCH] ARM: vexpress: refine dependencies for new code Arnd Bergmann
2014-05-27 9:18 ` Lee Jones [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=20140527091836.GE5875@lee--X1 \
--to=lee.jones@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pawel.moll@arm.com \
/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