Allow compile testing of TI PRU-ICSS Subsystem Platform drivers.
This allows for improved build-test coverage.
No functional change intended.
Signed-off-by: Simon Horman <[email protected]>
---
drivers/soc/ti/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/soc/ti/Kconfig b/drivers/soc/ti/Kconfig
index 8c2a1036bef5..2cae17b65fd9 100644
--- a/drivers/soc/ti/Kconfig
+++ b/drivers/soc/ti/Kconfig
@@ -85,7 +85,7 @@ config TI_K3_SOCINFO
config TI_PRUSS
tristate "TI PRU-ICSS Subsystem Platform drivers"
- depends on SOC_AM33XX || SOC_AM43XX || SOC_DRA7XX || ARCH_KEYSTONE || ARCH_K3
+ depends on SOC_AM33XX || SOC_AM43XX || SOC_DRA7XX || ARCH_KEYSTONE || ARCH_K3 || COMPILE_TEST
select MFD_SYSCON
help
TI PRU-ICSS Subsystem platform specific support.
Hi Simon Horman,
On Thu, 11 May 2023 16:54:36 +0200, Simon Horman wrote:
> Allow compile testing of TI PRU-ICSS Subsystem Platform drivers.
> This allows for improved build-test coverage.
>
> No functional change intended.
>
>
I have applied the following to branch ti-drivers-soc-next on [1].
NOTE: I did'nt see any immediate issue with this patch, but hopefully we dont
break COMPILE_TEST going ahead. Lets see.
Thank you!
[1/1] soc: ti: pruss: Allow compile-testing
commit: e752f9b924a1fd1afcf36e51b03dfa9c3096a3bd
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
On Wed, May 17, 2023 at 12:56:08PM -0500, Nishanth Menon wrote:
> Hi Simon Horman,
>
> On Thu, 11 May 2023 16:54:36 +0200, Simon Horman wrote:
> > Allow compile testing of TI PRU-ICSS Subsystem Platform drivers.
> > This allows for improved build-test coverage.
> >
> > No functional change intended.
> >
> >
>
> I have applied the following to branch ti-drivers-soc-next on [1].
> NOTE: I did'nt see any immediate issue with this patch, but hopefully we dont
> break COMPILE_TEST going ahead. Lets see.
> Thank you!
Thanks. I'll look out for any notices regarding breakage.
> [1/1] soc: ti: pruss: Allow compile-testing
> commit: e752f9b924a1fd1afcf36e51b03dfa9c3096a3bd
>
> All being well this means that it will be integrated into the linux-next
> tree (usually sometime in the next 24 hours) and sent up the chain during
> the next merge window (or sooner if it is a relevant bug fix), however if
> problems are discovered then the patch may be dropped or reverted.
>
> You may get further e-mails resulting from automated or manual testing
> and review of the tree, please engage with people reporting problems and
> send followup patches addressing any issues that are reported if needed.
>
> If any updates are required or you are submitting further changes they
> should be sent as incremental updates against current git, existing
> patches will not be replaced.
>
> Please add any relevant lists and maintainers to the CCs when replying
> to this mail.
>
> [1] git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
> --
> Regards,
> Nishanth Menon
> Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
>