From: Wolfram Sang <wsa@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>,
Krzysztof Adamski <krzysztof.adamski@nokia.com>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: axxia: use 'struct' for kernel-doc notation
Date: Fri, 20 Jan 2023 10:20:44 +0100 [thread overview]
Message-ID: <Y8pc7K2IWIlMYl6S@ninjato> (raw)
In-Reply-To: <20230113063756.14071-1-rdunlap@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
On Thu, Jan 12, 2023 at 10:37:56PM -0800, Randy Dunlap wrote:
> Add "struct" to prevent this kernel-doc warning:
>
> drivers/i2c/busses/i2c-axxia.c:135: warning: cannot understand function prototype: 'struct axxia_i2c_dev '
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Krzysztof Adamski <krzysztof.adamski@nokia.com>
> Cc: Wolfram Sang <wsa@kernel.org>
> Cc: linux-i2c@vger.kernel.org
Applied to for-current, thanks!
@Krzysztof: I hope you don't mind, I want to send out for-current soon.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-01-20 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 6:37 [PATCH] i2c: axxia: use 'struct' for kernel-doc notation Randy Dunlap
2023-01-20 9:20 ` Wolfram Sang [this message]
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=Y8pc7K2IWIlMYl6S@ninjato \
--to=wsa@kernel.org \
--cc=krzysztof.adamski@nokia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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