public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: <Claudiu.Beznea@microchip.com>
To: <alexandre.belloni@bootlin.com>
Cc: <mturquette@baylibre.com>, <sboyd@kernel.org>,
	<Nicolas.Ferre@microchip.com>, <krzysztof.kozlowski@linaro.org>,
	<linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/3] clk: at91: do not compile dt-compat.c for sama7g5 and sam9x60
Date: Thu, 8 Dec 2022 15:17:25 +0000	[thread overview]
Message-ID: <27ab1e71-6fdb-af0d-7dd1-a7731c1e2e95@microchip.com> (raw)
In-Reply-To: <Y5H3EH7kPOwGI2SQ@mail.local>

On 08.12.2022 16:39, Alexandre Belloni wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On 08/12/2022 13:45:15+0200, Claudiu Beznea wrote:
>> There is no need to have dt-compat.c compiled for SAMA7G5 and SAM9X60
>> as there is no in kernel device tree that could use it. Thus avoid
>> compiling dt-compat.c for them.
>>
> 
> Isn't it time to drop dt-compat.c? 

My assumption was that we need to guarantee that old device trees will
still work with newer kernels. Should we guarantee this only for a limited
period of time?

> I was going to send a patch after 6.1
> is released
> 
>> Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
>> ---
>>  drivers/clk/at91/Makefile | 16 ++++++++--------
>>  1 file changed, 8 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/clk/at91/Makefile b/drivers/clk/at91/Makefile
>> index 79301e1c1c36..89061b85e7d2 100644
>> --- a/drivers/clk/at91/Makefile
>> +++ b/drivers/clk/at91/Makefile
>> @@ -3,7 +3,7 @@
>>  # Makefile for at91 specific clk
>>  #
>>
>> -obj-y += pmc.o sckc.o dt-compat.o
>> +obj-y += pmc.o sckc.o
>>  obj-y += clk-slow.o clk-main.o clk-pll.o clk-plldiv.o clk-master.o
>>  obj-y += clk-system.o clk-peripheral.o clk-programmable.o
>>
>> @@ -15,12 +15,12 @@ obj-$(CONFIG_HAVE_AT91_H32MX)             += clk-h32mx.o
>>  obj-$(CONFIG_HAVE_AT91_GENERATED_CLK)        += clk-generated.o
>>  obj-$(CONFIG_HAVE_AT91_I2S_MUX_CLK)  += clk-i2s-mux.o
>>  obj-$(CONFIG_HAVE_AT91_SAM9X60_PLL)  += clk-sam9x60-pll.o
>> -obj-$(CONFIG_SOC_AT91RM9200) += at91rm9200.o
>> -obj-$(CONFIG_SOC_AT91SAM9) += at91sam9260.o at91sam9rl.o at91sam9x5.o
>> -obj-$(CONFIG_SOC_AT91SAM9) += at91sam9g45.o
>> -obj-$(CONFIG_SOC_AT91SAM9) += at91sam9n12.o at91sam9x5.o
>> +obj-$(CONFIG_SOC_AT91RM9200) += at91rm9200.o dt-compat.o
>> +obj-$(CONFIG_SOC_AT91SAM9) += at91sam9260.o at91sam9rl.o at91sam9x5.o dt-compat.o
>> +obj-$(CONFIG_SOC_AT91SAM9) += at91sam9g45.o dt-compat.o
>> +obj-$(CONFIG_SOC_AT91SAM9) += at91sam9n12.o at91sam9x5.o dt-compat.o
>>  obj-$(CONFIG_SOC_SAM9X60) += sam9x60.o
>> -obj-$(CONFIG_SOC_SAMA5D3) += sama5d3.o
>> -obj-$(CONFIG_SOC_SAMA5D4) += sama5d4.o
>> -obj-$(CONFIG_SOC_SAMA5D2) += sama5d2.o
>> +obj-$(CONFIG_SOC_SAMA5D3) += sama5d3.o dt-compat.o
>> +obj-$(CONFIG_SOC_SAMA5D4) += sama5d4.o dt-compat.o
>> +obj-$(CONFIG_SOC_SAMA5D2) += sama5d2.o dt-compat.o
>>  obj-$(CONFIG_SOC_SAMA7G5) += sama7g5.o
>> --
>> 2.34.1
>>
> 
> --
> Alexandre Belloni, co-owner and COO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com


  reply	other threads:[~2022-12-08 15:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 11:45 [PATCH 0/3] clk: at91: mark ddr clocks as critical Claudiu Beznea
2022-12-08 11:45 ` [PATCH 1/3] " Claudiu Beznea
2023-01-12 10:28   ` Claudiu.Beznea
2022-12-08 11:45 ` [PATCH 2/3] memory: atmel-sdramc: remove the driver Claudiu Beznea
2023-01-03 10:00   ` Claudiu.Beznea
2023-01-03 10:06     ` Krzysztof Kozlowski
2023-01-03 11:18       ` Claudiu.Beznea
2023-01-03 12:00         ` Krzysztof Kozlowski
2023-01-03 12:45           ` Claudiu.Beznea
2023-01-03 13:17             ` Krzysztof Kozlowski
2023-01-03 14:29               ` Claudiu.Beznea
2022-12-08 11:45 ` [PATCH 3/3] clk: at91: do not compile dt-compat.c for sama7g5 and sam9x60 Claudiu Beznea
2022-12-08 14:39   ` Alexandre Belloni
2022-12-08 15:17     ` Claudiu.Beznea [this message]
2023-01-12 10:28   ` Claudiu.Beznea

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=27ab1e71-6fdb-af0d-7dd1-a7731c1e2e95@microchip.com \
    --to=claudiu.beznea@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@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