From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] kernel-module-imx-gpu-viv: add new package
Date: Mon, 01 Feb 2016 22:28:21 +0100 [thread overview]
Message-ID: <87powg9l3e.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20160201215644.1e3d3713@free-electrons.com> (Thomas Petazzoni's message of "Mon, 1 Feb 2016 21:56:44 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
> I really don't like spreading hooks for package A in the code of
> package B. I think here it's better to change linux.mk with:
> $(if $(BR2_PACKAGE_KERNEL_MODULE_IMX_GPU_VIV),
> $(call KCONFIG_DISABLE_OPT,CONFIG_MXC_GPU_VIV,$(@D)/.config))
> In LINUX_KCONFIG_FIXUP_CMDS.
> Peter, Arnout, Yann, what do you think ?
Yes, that matches what we do for the other package related kernel
configs.
Does this theoretically work on a mainline kernel? If so, perhaps it
should also disable the recently added DRM_VIVANTE stuff in case it
conflicts?
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2016-02-01 21:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 9:36 [Buildroot] [PATCH 0/4] Update Freescale graphics packages Gary Bisson
2016-02-01 9:37 ` [Buildroot] [PATCH 1/4] imx-gpu-viv: bump version to 5.0.11 p7.1 Gary Bisson
2016-02-01 9:37 ` [Buildroot] [PATCH 2/4] xdriver_xf86-video-imx-viv: bump to version " Gary Bisson
2016-02-01 9:37 ` [Buildroot] [PATCH 3/4] kernel-module-imx-gpu-viv: add new package Gary Bisson
2016-02-01 20:56 ` Thomas Petazzoni
2016-02-01 21:28 ` Peter Korsgaard [this message]
2016-02-01 21:36 ` Yann E. MORIN
2016-02-01 23:33 ` Gary Bisson
2016-02-01 9:37 ` [Buildroot] [PATCH 4/4] configs/nitrogen6*: bump kernel version Gary Bisson
2016-02-01 20:53 ` [Buildroot] [PATCH 0/4] Update Freescale graphics packages Thomas Petazzoni
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=87powg9l3e.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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