From: Krzysztof Kozlowski <krzk@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"biju.das.au" <biju.das.au@gmail.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 3/5] watchdog: Make RZV2HWDT driver depend on ARCH_R9A09G47
Date: Fri, 24 Jan 2025 11:34:59 +0100 [thread overview]
Message-ID: <f4cdcb9e-ae30-45ad-87f4-7395db0ab995@kernel.org> (raw)
In-Reply-To: <TY3PR01MB11346DC4A22A2EC0CB0DAF61186E32@TY3PR01MB11346.jpnprd01.prod.outlook.com>
On 24/01/2025 11:20, Biju Das wrote:
>>
>>> + depends on ARCH_R9A09G047 || ARCH_R9A09G057 || COMPILE_TEST
>>
>> But this is just wrong. You are supposed to depend on renesas ARHC, not your individual SoC (and this
>> is what you called here "ARCH_R9A...").
>>
>> Greg many times gave strong opinion that even full ARCH is wrong and we managed to convince him that
>> it has a meaning (or he did not want to keep discussing). But restricting it per soc is pointless and
>> impossible to defend in discussion.
>
> Currently for building RZ/G3E WDT, I need to always have RZ/V2H SoC config.
> which is pointless. May be ARCH_RENESAS should ok in this case??
Assuming ARCH_RENESAS covers your individual SoCs above, yes, that's the
way for driver to limit themselves to usable family.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-24 10:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 10:38 [PATCH 0/5] Add support for RZ/G3E WDT Biju Das
2025-01-15 10:38 ` [PATCH 1/5] dt-bindings: watchdog: renesas,wdt: Document RZ/G3E support Biju Das
2025-01-18 15:51 ` Krzysztof Kozlowski
2025-01-23 10:15 ` Geert Uytterhoeven
2025-01-15 10:38 ` [PATCH 3/5] watchdog: Make RZV2HWDT driver depend on ARCH_R9A09G47 Biju Das
2025-01-15 14:55 ` Guenter Roeck
2025-01-15 17:17 ` Biju Das
2025-01-18 15:51 ` Krzysztof Kozlowski
2025-01-24 10:20 ` Biju Das
2025-01-24 10:34 ` Krzysztof Kozlowski [this message]
2025-01-24 10:57 ` Biju Das
2025-01-24 12:41 ` Krzysztof Kozlowski
2025-01-24 12:55 ` Biju Das
2025-01-24 13:00 ` Krzysztof Kozlowski
2025-01-24 13:10 ` Biju Das
2025-01-24 13:20 ` Krzysztof Kozlowski
2025-01-24 13:24 ` Biju Das
2025-01-24 13:40 ` Krzysztof Kozlowski
2025-01-24 13:51 ` Biju Das
2025-01-24 13:56 ` Geert Uytterhoeven
2025-01-19 14:28 ` [PATCH 0/5] Add support for RZ/G3E WDT Tommaso Merciai
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=f4cdcb9e-ae30-45ad-87f4-7395db0ab995@kernel.org \
--to=krzk@kernel.org \
--cc=biju.das.au@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=wim@linux-watchdog.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