diff options
| author | Mark Brown <broonie@kernel.org> | 2026-07-19 23:55:50 +0100 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2026-07-19 23:55:50 +0100 |
| commit | b247067fb1df78e9dfaf6d609774bf0caedb9c75 (patch) | |
| tree | c594131c32a78d9d7985c583b0a05811af702119 /tools/perf/scripts/python/bin | |
| parent | 787dc62517039ecb72c473b4d2681b9775b2af9b (diff) | |
| parent | 7720f98d08fddd21369ddfe048900cc89efd99b3 (diff) | |
spi: axiado: cond_no_effect and kernel-doc fixes
Babanpreet Singh <bbnpreetsingh@gmail.com> says:
Two small cleanups for the Axiado SPI driver, both defects present
since the driver was added in e75a6b00ad79 ("spi: axiado: Add driver
for Axiado SPI DB controller").
Patch 1 addresses the coccinelle cond_no_effect warning reported by
the kernel test robot on 2026-07-12 [1]: the RX-only/full-duplex
else-if arm and the trailing else arm in ax_transfer_one() have
identical bodies, so the second condition has no effect. The arms are
merged; no functional change (on x86_64/gcc 14, only
ax_transfer_one()'s object code changes, dropping the dead condition
evaluation).
Patch 2 fixes the kernel-doc comments in the driver: a copy-pasted
function name on ax_spi_get_rx_byte_for_irq(), a /** block with no
identifier line on ax_spi_process_rx_and_finalize(), and stale/missing
member documentation on struct ax_spi. This silences the driver's two
W=1 kernel-doc warnings plus five more visible when kernel-doc is run
on the header directly.
Both patches are against spi/for-next; they are independent of each
other except for touching the same file.
[1] https://lore.kernel.org/r/202607121827.djB0zLAj-lkp@intel.com/
Link: https://patch.msgid.link/20260713060807.7-1-bbnpreetsingh@gmail.com
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions
