Struct attribute names must be an exact match or the kerneldoc checker
gets confused.

Fixes the following W=1 kernel build warning(s):

 drivers/dma/mediatek/mtk-hsdma.c:120: warning: Function parameter or member 
'desc1' not described in 'mtk_hsdma_pdesc'
 drivers/dma/mediatek/mtk-hsdma.c:120: warning: Function parameter or member 
'desc2' not described in 'mtk_hsdma_pdesc'
 drivers/dma/mediatek/mtk-hsdma.c:120: warning: Function parameter or member 
'desc3' not described in 'mtk_hsdma_pdesc'
 drivers/dma/mediatek/mtk-hsdma.c:120: warning: Function parameter or member 
'desc4' not described in 'mtk_hsdma_pdesc'

Cc: Sean Wang <[email protected]>
Cc: Matthias Brugger <[email protected]>
Cc: [email protected]
Signed-off-by: Lee Jones <[email protected]>
---
 drivers/dma/mediatek/mtk-hsdma.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/dma/mediatek/mtk-hsdma.c b/drivers/dma/mediatek/mtk-hsdma.c
index 4c58da7421432..f133ae8dece16 100644
--- a/drivers/dma/mediatek/mtk-hsdma.c
+++ b/drivers/dma/mediatek/mtk-hsdma.c
@@ -107,10 +107,10 @@ enum mtk_hsdma_vdesc_flag {
  * struct mtk_hsdma_pdesc - This is the struct holding info describing physical
  *                         descriptor (PD) and its placement must be kept at
  *                         4-bytes alignment in little endian order.
- * @desc[1-4]:             The control pad used to indicate hardware how to
- *                         deal with the descriptor such as source and
- *                         destination address and data length. The maximum
- *                         data length each pdesc can handle is 0x3f80 bytes
+ * @desc1:                 | The control pad used to indicate hardware how to
+ * @desc2:                 | deal with the descriptor such as source and
+ * @desc3:                 | destination address and data length. The maximum
+ * @desc4:                 | data length each pdesc can handle is 0x3f80 bytes
  */
 struct mtk_hsdma_pdesc {
        __le32 desc1;
-- 
2.25.1

Reply via email to