From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c: meson: update doc description to fix build warnings
Date: Fri, 26 Jan 2018 18:34:08 +0100 [thread overview]
Message-ID: <20180126173408.oytldtdhh3mlezak@ninjato> (raw)
In-Reply-To: <20180124070514.183119-1-yixun.lan@amlogic.com>
On Wed, Jan 24, 2018 at 03:05:14PM +0800, Yixun Lan wrote:
> Add description for 'data' parameter and drop unused 'irq' memeber.
>
> Here is the warnings:
> drivers/i2c/busses/i2c-meson.c:103: warning: No description found for
> parameter 'data'
> drivers/i2c/busses/i2c-meson.c:103: warning: Excess struct member 'irq'
> description in 'meson_i2c'
>
> Suggested-by: Wolfram Sang <wsa@the-dreams.de>
> Signed-off-by: Yixun Lan <yixun.lan@amlogic.com>
Applied to for-next, thanks!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180126/e629d88c/attachment.sig>
prev parent reply other threads:[~2018-01-26 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 7:05 [PATCH] i2c: meson: update doc description to fix build warnings Yixun Lan
2018-01-26 17:34 ` 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=20180126173408.oytldtdhh3mlezak@ninjato \
--to=wsa@the-dreams.de \
--cc=linux-arm-kernel@lists.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