From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Kai Song <songkai01@inspur.com>, linuxppc-dev@lists.ozlabs.org
Cc: paulus@samba.org, oohall@gmail.com, linux-kernel@vger.kernel.org,
dja@axtens.net
Subject: Re: [PATCH] powerpc/eeh: Fix docstrings in eeh.c
Date: Sun, 17 Oct 2021 23:32:08 +1100 [thread overview]
Message-ID: <163447392810.1159469.11303329795231824264.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20211009041630.4135-1-songkai01@inspur.com>
On Sat, 9 Oct 2021 12:16:30 +0800, Kai Song wrote:
> We fix the following warnings when building kernel with W=1:
> arch/powerpc/kernel/eeh.c:598: warning: Function parameter or member 'function' not described in 'eeh_pci_enable'
> arch/powerpc/kernel/eeh.c:774: warning: Function parameter or member 'edev' not described in 'eeh_set_dev_freset'
> arch/powerpc/kernel/eeh.c:774: warning: expecting prototype for eeh_set_pe_freset(). Prototype was for eeh_set_dev_freset() instead
> arch/powerpc/kernel/eeh.c:814: warning: Function parameter or member 'include_passed' not described in 'eeh_pe_reset_full'
> arch/powerpc/kernel/eeh.c:944: warning: Function parameter or member 'ops' not described in 'eeh_init'
> arch/powerpc/kernel/eeh.c:1451: warning: Function parameter or member 'include_passed' not described in 'eeh_pe_reset'
> arch/powerpc/kernel/eeh.c:1526: warning: Function parameter or member 'func' not described in 'eeh_pe_inject_err'
> arch/powerpc/kernel/eeh.c:1526: warning: Excess function parameter 'function' described in 'eeh_pe_inject_err'
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/eeh: Fix docstrings in eeh.c
https://git.kernel.org/powerpc/c/b616230e2325e5560330c40172a4d4e4c5da2c59
cheers
prev parent reply other threads:[~2021-10-17 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 4:16 [PATCH] powerpc/eeh: Fix docstrings in eeh.c Kai Song
2021-10-17 12:32 ` Michael Ellerman [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=163447392810.1159469.11303329795231824264.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=dja@axtens.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oohall@gmail.com \
--cc=paulus@samba.org \
--cc=songkai01@inspur.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).