From: Greg KH <gregkh@linuxfoundation•org>
To: Lee Jones <lee.jones@linaro•org>
Cc: Boris Brezillon <boris.brezillon@free-electrons•com>,
Alexandre Belloni <alexandre.belloni@bootlin•com>,
linux-kernel@vger•kernel.org, stable@vger•kernel.org,
Ludovic Desroches <ludovic.desroches@microchip•com>,
linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH 09/10] mfd: atmel-smc: Add missing colon(s) for 'conf' arguments
Date: Thu, 25 Jun 2020 08:55:45 +0200 [thread overview]
Message-ID: <20200625065545.GA2789306@kroah.com> (raw)
In-Reply-To: <20200625064619.2775707-10-lee.jones@linaro.org>
On Thu, Jun 25, 2020 at 07:46:18AM +0100, Lee Jones wrote:
> Kerneldoc valication gets confused if syntax isn't "@.*: ".
>
> Adding the missing colons squashes the following W=1 warnings:
>
> drivers/mfd/atmel-smc.c:247: warning: Function parameter or member 'conf' not described in 'atmel_smc_cs_conf_apply'
> drivers/mfd/atmel-smc.c:268: warning: Function parameter or member 'conf' not described in 'atmel_hsmc_cs_conf_apply'
Why is this a stable patch?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-06-25 6:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 6:46 [PATCH 00/10] Fix a bunch more W=1 warnings in MFD Lee Jones
2020-06-25 6:46 ` [PATCH 01/10] mfd: wm8350-core: Supply description wm8350_reg_{un}lock args Lee Jones
2020-06-25 6:56 ` Greg KH
2020-06-25 7:13 ` Lee Jones
2020-06-25 9:45 ` Greg KH
2020-06-25 13:34 ` Lee Jones
2020-06-25 13:24 ` Jonathan Corbet
2020-06-25 13:38 ` Lee Jones
2020-06-25 6:46 ` [PATCH 02/10] mfd: mfd-core: Complete kerneldoc header for devm_mfd_add_devices() Lee Jones
2020-07-01 19:33 ` Sasha Levin
2020-07-02 6:36 ` Lee Jones
2020-07-10 14:02 ` Sasha Levin
2020-06-25 6:46 ` [PATCH 03/10] mfd: db8500-prcmu: Add description for 'reset_reason' in kerneldoc Lee Jones
2020-07-07 12:39 ` Linus Walleij
2020-06-25 6:46 ` [PATCH 04/10] mfd: db8500-prcmu: Remove incorrect function header from .probe() function Lee Jones
2020-07-07 12:39 ` Linus Walleij
2020-06-25 6:46 ` [PATCH 05/10] mfd: omap-usb-host: Remove invalid use of kerneldoc syntax Lee Jones
2020-06-25 6:46 ` [PATCH 06/10] mfd: omap-usb-host: Provide description for 'pdev' argument to .probe() Lee Jones
2020-06-25 6:46 ` [PATCH 07/10] mfd: omap-usb-tll: " Lee Jones
2020-06-25 6:46 ` [PATCH 08/10] mfd: atmel-smc: Silence comparison of unsigned expression < 0 is always false warning (W=1) Lee Jones
2020-06-26 20:56 ` Alexandre Belloni
2020-06-30 12:10 ` Lee Jones
2020-06-25 6:46 ` [PATCH 09/10] mfd: atmel-smc: Add missing colon(s) for 'conf' arguments Lee Jones
2020-06-25 6:55 ` Greg KH [this message]
2020-06-26 20:56 ` Alexandre Belloni
2020-07-01 19:33 ` Sasha Levin
2020-07-02 6:36 ` Lee Jones
2020-07-10 14:02 ` Sasha Levin
2020-06-25 6:46 ` [PATCH 10/10] mfd: altera-sysmgr: Supply descriptions for 'np' and 'property' function args Lee Jones
2020-07-01 19:33 ` Sasha Levin
2020-07-02 6:35 ` Lee Jones
2020-07-10 14:02 ` Sasha Levin
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=20200625065545.GA2789306@kroah.com \
--to=gregkh@linuxfoundation$(echo .)org \
--cc=alexandre.belloni@bootlin$(echo .)com \
--cc=boris.brezillon@free-electrons$(echo .)com \
--cc=lee.jones@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=ludovic.desroches@microchip$(echo .)com \
--cc=stable@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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