public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alvin Šipraga" <ALSI@bang-olufsen.dk>
To: kernel test robot <lkp@intel.com>
Cc: "Alvin Šipraga" <alvin@pqrs.dk>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
	"kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/4] usb: typec: add TUSB320xA driver
Date: Tue, 1 Mar 2022 17:20:51 +0000	[thread overview]
Message-ID: <87h78h8u8d.fsf@bang-olufsen.dk> (raw)
In-Reply-To: <202203020056.igXsHYzi-lkp@intel.com> (kernel test robot's message of "Wed, 2 Mar 2022 00:58:06 +0800")

kernel test robot <lkp@intel.com> writes:

> Hi "Alvin,
>
> I love your patch! Perhaps something to improve:
>

<snip>

>
> All warnings (new ones prefixed by >>):
>
>>> drivers/usb/typec/tusb320xa.c:407:6: warning: no previous prototype for 'tusb320xa_action_role_sw_put' [-Wmissing-prototypes]
>      407 | void tusb320xa_action_role_sw_put(void *data)
>          |      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> drivers/usb/typec/tusb320xa.c:414:6: warning: no previous prototype for 'tusb320xa_action_unregister_port' [-Wmissing-prototypes]
>      414 | void tusb320xa_action_unregister_port(void *data)
>          |      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Ah yes, these should be static, will fix in v2. Thank you, test robot.

>
>
> vim +/tusb320xa_action_role_sw_put +407 drivers/usb/typec/tusb320xa.c
>
>    406	
>  > 407	void tusb320xa_action_role_sw_put(void *data)
>    408	{
>    409		struct usb_role_switch *role_sw = data;
>    410	
>    411		usb_role_switch_put(role_sw);
>    412	}
>    413	
>  > 414	void tusb320xa_action_unregister_port(void *data)
>    415	{
>    416		struct typec_port *port = data;
>    417	
>    418		typec_unregister_port(port);
>    419	}
>    420	
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

  reply	other threads:[~2022-03-01 17:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 13:20 [PATCH 0/4] usb: typec: add drivers for TUSB320xA and TS5USBA224 Alvin Šipraga
2022-03-01 13:20 ` [PATCH 1/4] dt-bindings: usb: add TUSB320xA Type-C port controller Alvin Šipraga
2022-03-02 18:16   ` Rob Herring
2022-03-01 13:20 ` [PATCH 2/4] dt-bindings: usb: add TS5USBA224 USB/Audio switch mux Alvin Šipraga
2022-03-02 18:21   ` Rob Herring
2022-03-02 18:58     ` Alvin Šipraga
2022-03-01 13:20 ` [PATCH 3/4] usb: typec: add TUSB320xA driver Alvin Šipraga
2022-03-01 16:58   ` kernel test robot
2022-03-01 17:20     ` Alvin Šipraga [this message]
2022-03-07 14:36   ` Heikki Krogerus
2022-03-07 22:17     ` Alvin Šipraga
2022-03-08 11:49       ` Heikki Krogerus
2022-03-08 12:30         ` Alvin Šipraga
2022-03-01 13:20 ` [PATCH 4/4] usb: typec: mux: add TS5USBA224 driver Alvin Šipraga

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=87h78h8u8d.fsf@bang-olufsen.dk \
    --to=alsi@bang-olufsen.dk \
    --cc=alvin@pqrs.dk \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=robh+dt@kernel.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