From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Péter Ujfalusi" <peter.ujfalusi@gmail.com>,
"Vinod Koul" <vkoul@kernel.org>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dmaengine: ti: Do not enable by default during compile testing
Date: Sun, 6 Apr 2025 19:43:05 +0200 [thread overview]
Message-ID: <2f0e8807-d37c-4491-be6e-c04e3e9032e6@linaro.org> (raw)
In-Reply-To: <033fe56b-3f07-4fa7-98a1-84ad53034ace@gmail.com>
On 06/04/2025 18:08, Péter Ujfalusi wrote:
>
>
> On 4/4/25 3:21 PM, Krzysztof Kozlowski wrote:
>> Enabling the compile test should not cause automatic enabling of all
>> drivers.
>
> The scope of compile test has changed?
No, it's the same.
> These drivers will likely not going to be compile tested from now on in
Why? They are. That's why allyesconfig you have.
> practice on other that the platforms they are used?
>
> It gave a piece of mind to know that the code compiles on ppc/x86/etc
> also or it is no longer important sanity check?
And nothing changes here. They will be compile tested on all these other
archs the same as all other arch/soc specific drivers, which do exactly
what I am doing here.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-04-06 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 12:21 [PATCH 1/2] dmaengine: sh: Do not enable SH_DMAE_BASE " Krzysztof Kozlowski
2025-04-04 12:21 ` [PATCH 2/2] dmaengine: ti: Do not enable " Krzysztof Kozlowski
2025-04-06 16:08 ` Péter Ujfalusi
2025-04-06 17:43 ` Krzysztof Kozlowski [this message]
2025-05-22 18:35 ` [PATCH 1/2] dmaengine: sh: Do not enable SH_DMAE_BASE " Krzysztof Kozlowski
2025-06-26 22:48 ` Vinod Koul
2025-07-08 13:07 ` Geert Uytterhoeven
2025-07-08 13:21 ` Krzysztof Kozlowski
2025-07-08 13:31 ` Geert Uytterhoeven
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=2f0e8807-d37c-4491-be6e-c04e3e9032e6@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=vkoul@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®