public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <niklas.cassel@linaro.org>
To: Vivek Gautam <vivek.gautam@codeaurora.org>
Cc: Andy Gross <andy.gross@linaro.org>,
	David Brown <david.brown@linaro.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	linux-soc@vger.kernel.org,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/5] soc: qcom: Remove depends on ARCH_QCOM
Date: Thu, 14 Jun 2018 10:31:16 +0200	[thread overview]
Message-ID: <20180614083116.GA18093@centauri.lan> (raw)
In-Reply-To: <CAFp+6iEfd_iBCUtuYbe+vsc31BSC2UVee6YNNSGX5XxMMjJ=aA@mail.gmail.com>

On Thu, Jun 14, 2018 at 12:08:10PM +0530, Vivek Gautam wrote:
> On Thu, Jun 14, 2018 at 12:05 PM, Vivek Gautam
> <vivek.gautam@codeaurora.org> wrote:
> > On Wed, Jun 13, 2018 at 6:24 PM, Niklas Cassel <niklas.cassel@linaro.org> wrote:
> >> Since commit cab673583d96 ("soc: Unconditionally include qcom Makefile"),
> >> we unconditionally include the soc/qcom/Makefile.
> >>
> >> This opens up the possibility to compile test the code even when
> >> building for other architectures.
> >
> > Why do we want to do this when all of it is qcom specific?
> > Besides, wouldn't this increase the binary size for other platforms.

To be able to compile test drivers that select some of these Kconfigs,
even when building for other architectures.

The binary size shouldn't increase if they don't enable these Kconfigs.

> 
> Sorry, my bad. Send the message without completing.
> 
> Besides above points, the COMPILE_TEST flag should allow you
> to compile test all of these drivers. If COMPILE_TEST is missing
> in some of the configs, we should try adding that.
> Or, is there anything that I am missing here for the intention of this patch?

That is another alternative.
So either make sure that all these Kconfigs
have "depends on ARCH_QCOM || COMPILE_TEST",
or
remove ARCH_QCOM from these Kconfigs.

A third, and perhaps best alternative is to do like
drivers/soc/mediatek/Kconfig

menu "MediaTek SoC drivers"
    depends on ARCH_MEDIATEK || COMPILE_TEST

Make sure that our root menu entry depends on ARCH_QCOM || COMPILE_TEST,
that way we could remove ARCH_QCOM for all Kconfigs.

Thoughts?


Regards,
Niklas

  reply	other threads:[~2018-06-14  8:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13 12:53 [PATCH 0/5] soc: qcom: remove depends on ARCH_QCOM Niklas Cassel
2018-06-13 12:53 ` [PATCH 1/5] rpmsg: smd: Add missing include of sizes.h Niklas Cassel
2018-06-13 13:16   ` Niklas Cassel
2018-06-13 12:53 ` [PATCH 2/5] soc: qcom: smem: " Niklas Cassel
2018-06-13 12:53 ` [PATCH 3/5] soc: qcom: smp2p: Add select IRQ_DOMAIN Niklas Cassel
2018-06-13 12:53 ` [PATCH 4/5] soc: qcom: smsm: " Niklas Cassel
2018-06-13 12:54 ` [PATCH 5/5] soc: qcom: Remove depends on ARCH_QCOM Niklas Cassel
2018-06-13 13:48   ` Niklas Cassel
2018-06-13 16:51   ` kbuild test robot
2018-06-13 21:44   ` kbuild test robot
2018-06-14  6:35   ` Vivek Gautam
2018-06-14  6:38     ` Vivek Gautam
2018-06-14  8:31       ` Niklas Cassel [this message]
2018-06-14 10:24         ` Vivek Gautam

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=20180614083116.GA18093@centauri.lan \
    --to=niklas.cassel@linaro.org \
    --cc=andy.gross@linaro.org \
    --cc=david.brown@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=vivek.gautam@codeaurora.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