From: David Miller <davem@davemloft.net>
To: lkp@intel.com
Cc: kbuild-all@lists.01.org, bkkarthik@pesu.pes.edu,
linux-kernel@vger.kernel.org, jmaloy@redhat.com,
netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
ying.xue@windriver.com, kuba@kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] [PATCH] net: tipc: fix general protection fault in tipc_conn_delete_sub
Date: Mon, 27 Jul 2020 12:38:54 -0700 (PDT) [thread overview]
Message-ID: <20200727.123854.863832576284265842.davem@davemloft.net> (raw)
In-Reply-To: <202007272337.Rd2io2fw%lkp@intel.com>
From: kernel test robot <lkp@intel.com>
Date: Mon, 27 Jul 2020 23:52:50 +0800
> All warnings (new ones prefixed by >>):
>
> net/tipc/topsrv.c: In function 'tipc_conn_send_to_sock':
>>> net/tipc/topsrv.c:259:10: warning: 'return' with a value, in function returning void [-Wreturn-type]
> 259 | return -EINVAL;
> | ^
> net/tipc/topsrv.c:247:13: note: declared here
> 247 | static void tipc_conn_send_to_sock(struct tipc_conn *con)
> | ^~~~~~~~~~~~~~~~~~~~~~
Please look at the compiler output when you submit changes.
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
prev parent reply other threads:[~2020-07-27 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 13:10 [Linux-kernel-mentees] [PATCH] net: tipc: fix general protection fault in tipc_conn_delete_sub B K Karthik
2020-07-27 13:22 ` Greg KH
2020-07-27 14:16 ` B K Karthik
2020-07-27 14:24 ` Greg KH
2020-07-28 16:15 ` Ying Xue
2020-07-27 15:52 ` kernel test robot
2020-07-27 19:38 ` David Miller [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=20200727.123854.863832576284265842.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bkkarthik@pesu.pes.edu \
--cc=jmaloy@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.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).