From: Mark Brown <broonie@kernel.org>
To: Tamara Diaconita <diaconitatamara@gmail.com>
Cc: lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
outreachy-kernel@googlegroups.com, corbet@lwn.net,
Tamara Diaconita <diaconita.tamara@gmail.com>
Subject: Re: [PATCH] Regulator: core.c: Fix kerneldoc comments
Date: Wed, 29 Mar 2017 11:36:11 +0100 [thread overview]
Message-ID: <20170329103611.266sdjhh75vzozfq@sirena.org.uk> (raw)
In-Reply-To: <20170328183021.2683-1-diaconita.tamara@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
On Tue, Mar 28, 2017 at 09:30:21PM +0300, Tamara Diaconita wrote:
> Remove the description for the non-existing 'ret' to fix the build warning:
> ./drivers/regulator/core.c:1467: warning:
> Excess function parameter 'ret' description in 'regulator_dev_lookup'.
> The description found for the return value is: @ret: 0 on success, -ENODEV
> if lookup fails permanently, -EPROBE_DEFER if lookup could succeed in the future.
Please word wrap your commit messages within paragraphs at something
substantially less than 80 columns. Doing this makes your messages much
easier to read and reply to and ensures that the changelogs display well
in the git UI.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-03-29 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 18:30 [PATCH] Regulator: core.c: Fix kerneldoc comments Tamara Diaconita
2017-03-28 19:51 ` [Outreachy kernel] " Julia Lawall
2017-03-29 10:36 ` Mark Brown [this message]
2017-03-29 11:02 ` Applied "regulator: core: Fix kerneldoc comments" to the regulator tree Mark Brown
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=20170329103611.266sdjhh75vzozfq@sirena.org.uk \
--to=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=diaconita.tamara@gmail.com \
--cc=diaconitatamara@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
/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;
as well as URLs for NNTP newsgroup(s).