mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Jesse Taube" <mr.bossman075@gmail.com>,
	"Arnd Bergmann" <arnd@kernel.org>,
	"Abel Vesa" <abelvesa@kernel.org>,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Stephen Boyd" <sboyd@kernel.org>,
	"Shawn Guo" <shawnguo@kernel.org>,
	"Sascha Hauer" <s.hauer@pengutronix.de>
Cc: "Pengutronix Kernel Team" <kernel@pengutronix.de>,
	"Fabio Estevam" <festevam@gmail.com>,
	"NXP Linux Team" <linux-imx@nxp.com>,
	"Peng Fan" <peng.fan@nxp.com>,
	"Giulio Benetti" <giulio.benetti@benettiengineering.com>,
	"Dario Binacchi" <dario.binacchi@amarulasolutions.com>,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: imx: fix compile testing imxrt1050
Date: Fri, 16 Dec 2022 09:24:42 +0100	[thread overview]
Message-ID: <abb5af81-0f0c-4457-9562-8f29da4c85b7@app.fastmail.com> (raw)
In-Reply-To: <f7f57361-8a4b-00e4-57fe-0ed103ddb10e@gmail.com>

On Thu, Dec 15, 2022, at 21:15, Jesse Taube wrote:
> On 12/15/22 11:58, Arnd Bergmann wrote:

>>   config CLK_IMXRT1050
>>   	tristate "IMXRT1050 CCM Clock Driver"
>> -	depends on SOC_IMXRT
>> +	depends on SOC_IMXRT || COMPILE_TEST
> Not sure what COMPILE_TEST is but,

The idea is that you can enable the driver to be built in
allmodconfig or randconfig regardless of the architecture,
to see any compiler-time warnings creeping up without
having to build an imxrt specific kernel.

> Acked-by: Jesse Taube <Mr.Bossman075@gmail.com>

Thanks

   Arnd

  reply	other threads:[~2022-12-16  8:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 16:58 Arnd Bergmann
2022-12-15 20:15 ` Jesse Taube
2022-12-16  8:24   ` Arnd Bergmann [this message]
2023-01-09 10:50 ` Abel Vesa
2023-02-10 23:26 ` Stephen Boyd

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=abb5af81-0f0c-4457-9562-8f29da4c85b7@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=abelvesa@kernel.org \
    --cc=arnd@kernel.org \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=festevam@gmail.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mr.bossman075@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=peng.fan@nxp.com \
    --cc=s.hauer@pengutronix.de \
    --cc=sboyd@kernel.org \
    --cc=shawnguo@kernel.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
all inboxes | Powered by JetHome®