From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Chintan Vankar <c-vankar@ti.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
Arnd Bergmann <arnd@arndb.de>, Eric Biggers <ebiggers@kernel.org>,
Nishanth Menon <nm@ti.com>, Michal Simek <michal.simek@amd.com>,
Luca Weiss <luca.weiss@fairphone.com>,
Sven Peter <sven@kernel.org>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: linux-kernel@vger.kernel.org, s-vadapalli@ti.com, danishanwar@ti.com
Subject: Re: [PATCH] arm64: defconfig: Enable configs for traffic classifier and action module
Date: Fri, 20 Feb 2026 22:07:22 +0100 [thread overview]
Message-ID: <341cb762-a87c-45f2-9351-34af16ef0a4d@oss.qualcomm.com> (raw)
In-Reply-To: <e66773a4-28b5-41ce-9fcf-a120baa15afc@ti.com>
On 20/02/2026 21:53, Chintan Vankar wrote:
> Hello Krzysztof,
>
> On 20/02/26 12:40, Krzysztof Kozlowski wrote:
>> On 19/02/2026 17:48, Chintan Vankar wrote:
>>> Enable CONFIG_NET_CLS_U32 and CONFIG_NET_ACT_SKBEDIT as modules to allow
>>> traffic control operations that can be used during TSN (Time Sensitive
>>> Networking) testing.
>>
>> Why do we need it in the defconfig? This is not a full blown distro
>> config, so any tests of user space or of other non-SoC features by
>> design require multiple other options.
>>
>
> I agree to your point, these options are not strictly required for arm64
> platform for an essential features. They are added to simplify TSN
> feature validation as I mentioned in the commit message.
I don't get why do we need defconfig to validate TSN feature, if this is
not a hardware feature. Unless it is and you actually need it for
drivers, but then commit msg is incomplete.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-02-20 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 16:48 Chintan Vankar
2026-02-20 7:10 ` Krzysztof Kozlowski
2026-02-20 20:53 ` Chintan Vankar
2026-02-20 21:07 ` Krzysztof Kozlowski [this message]
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=341cb762-a87c-45f2-9351-34af16ef0a4d@oss.qualcomm.com \
--to=krzysztof.kozlowski@oss.qualcomm.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=c-vankar@ti.com \
--cc=danishanwar@ti.com \
--cc=ebiggers@kernel.org \
--cc=geert+renesas@glider.be \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=michal.simek@amd.com \
--cc=nm@ti.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=s-vadapalli@ti.com \
--cc=sven@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®