[v2,0/2] Fix compilation errors with pruss APIs

Message

MD Danish Anwar Dec. 20, 2024, 10:05 a.m. UTC

The APIs in 'include/linux/pruss_driver.h' produce compilation errors and
warnings when config symbol CONFIG_TI_PRUSS is not enabled.

This series fixes those errors / warnings.

Also the header file 'include/linux/pruss_driver.h' is orphan and has no
entry in MAINTAINERS file.

v2 - v1:
*) Collected RB tag from Roger for PATCH 1/2
*) Fixed typo in PATCH 2/2 as suggested by Roger.

v1 https://lore.kernel.org/all/[e-mail]/

MD Danish Anwar (2):
  soc: ti: pruss: Fix pruss APIs
  MAINTAINERS: Add entry for linux/pruss_driver.h

 MAINTAINERS                  |  1 +
 include/linux/pruss_driver.h | 12 ++++++------
 2 files changed, 7 insertions(+), 6 deletions(-)


base-commit: 8503810115fbff903f626adc0788daa048302bc0

Comments

Nishanth Menon Jan. 2, 2025, 4:41 p.m. UTC | #1

Hi MD Danish Anwar,

On Fri, 20 Dec 2024 15:35:06 +0530, MD Danish Anwar wrote:
> The APIs in 'include/linux/pruss_driver.h' produce compilation errors and
> warnings when config symbol CONFIG_TI_PRUSS is not enabled.
> 
> This series fixes those errors / warnings.
> 
> Also the header file 'include/linux/pruss_driver.h' is orphan and has no
> entry in MAINTAINERS file.
> 
> [...]

I have applied the following to branch ti-drivers-soc-next on [1].

[1/2] soc: ti: pruss: Fix pruss APIs
      commit: 202580b60229345dc2637099f10c8a8857c1fdc2

I have applied the following to branch ti-k3-maintainer-next on [1].

[2/2] MAINTAINERS: Add entry for linux/pruss_driver.h
      commit: 31bd1f4517b651e132fae7cbb5f63b190015da94

Thank you!

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] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git