public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn•ch>
To: Lee Jones <lee.jones@linaro•org>
Cc: Geoff Levand <geoff@infradead•org>,
	linux-kernel@vger•kernel.org,
	Jens Osterkamp <Jens.Osterkamp@de•ibm.com>,
	netdev@vger•kernel.org, Paul Mackerras <paulus@samba•org>,
	Utz Bacher <utz.bacher@de•ibm.com>,
	Jakub Kicinski <kuba@kernel•org>,
	linuxppc-dev@lists•ozlabs.org,
	"David S. Miller" <davem@davemloft•net>
Subject: Re: [PATCH 6/8] net: ethernet: toshiba: ps3_gelic_net: Fix some kernel-doc misdemeanours
Date: Sun, 29 Nov 2020 19:45:45 +0100	[thread overview]
Message-ID: <20201129184545.GM2234159@lunn.ch> (raw)
In-Reply-To: <20201126133853.3213268-7-lee.jones@linaro.org>

On Thu, Nov 26, 2020 at 01:38:51PM +0000, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
> 
>  drivers/net/ethernet/toshiba/ps3_gelic_net.c:1107: warning: Function parameter or member 'irq' not described in 'gelic_card_interrupt'
>  drivers/net/ethernet/toshiba/ps3_gelic_net.c:1107: warning: Function parameter or member 'ptr' not described in 'gelic_card_interrupt'
>  drivers/net/ethernet/toshiba/ps3_gelic_net.c:1407: warning: Function parameter or member 'txqueue' not described in 'gelic_net_tx_timeout'
>  drivers/net/ethernet/toshiba/ps3_gelic_net.c:1439: warning: Function parameter or member 'napi' not described in 'gelic_ether_setup_netdev_ops'
>  drivers/net/ethernet/toshiba/ps3_gelic_net.c:1639: warning: Function parameter or member 'dev' not described in 'ps3_gelic_driver_probe'
>  drivers/net/ethernet/toshiba/ps3_gelic_net.c:1795: warning: Function parameter or member 'dev' not described in 'ps3_gelic_driver_remove'
> 
> Cc: Geoff Levand <geoff@infradead•org>
> Cc: "David S. Miller" <davem@davemloft•net>
> Cc: Jakub Kicinski <kuba@kernel•org>
> Cc: Michael Ellerman <mpe@ellerman•id.au>
> Cc: Benjamin Herrenschmidt <benh@kernel•crashing.org>
> Cc: Paul Mackerras <paulus@samba•org>
> Cc: Utz Bacher <utz.bacher@de•ibm.com>
> Cc: Jens Osterkamp <Jens.Osterkamp@de•ibm.com>
> Cc: netdev@vger•kernel.org
> Cc: linuxppc-dev@lists•ozlabs.org
> Signed-off-by: Lee Jones <lee.jones@linaro•org>

Reviewed-by: Andrew Lunn <andrew@lunn•ch>

    Andrew

  reply	other threads:[~2020-11-29 18:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 13:38 [PATCH 0/8] Rid W=1 warnings in Net Lee Jones
2020-11-26 13:38 ` [PATCH 5/8] net: ethernet: ibm: ibmvnic: Fix some kernel-doc misdemeanours Lee Jones
2020-11-29 18:43   ` Andrew Lunn
2020-11-30  9:04     ` Lee Jones
2020-11-26 13:38 ` [PATCH 6/8] net: ethernet: toshiba: ps3_gelic_net: " Lee Jones
2020-11-29 18:45   ` Andrew Lunn [this message]
2020-11-26 13:38 ` [PATCH 8/8] net: ethernet: ibm: ibmvnic: Fix some kernel-doc issues Lee Jones
2020-11-29 19:10   ` Andrew Lunn
2020-11-30  8:59     ` Lee Jones
2020-11-27 17:39 ` [PATCH 0/8] Rid W=1 warnings in Net Jakub Kicinski

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=20201129184545.GM2234159@lunn.ch \
    --to=andrew@lunn$(echo .)ch \
    --cc=Jens.Osterkamp@de$(echo .)ibm.com \
    --cc=davem@davemloft$(echo .)net \
    --cc=geoff@infradead$(echo .)org \
    --cc=kuba@kernel$(echo .)org \
    --cc=lee.jones@linaro$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=paulus@samba$(echo .)org \
    --cc=utz.bacher@de$(echo .)ibm.com \
    /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