From: David Miller <davem@davemloft.net>
To: fengguang.wu@intel.com
Cc: kbuild-internal@linux.intel.com, lkp@eclists.intel.com,
kbuild-all@01.org, netdev@vger.kernel.org
Subject: Re: [RFC PATCH net-next] tipc: link_is_bc_sndlink() can be static
Date: Sun, 25 Oct 2015 06:34:11 -0700 (PDT) [thread overview]
Message-ID: <20151025.063411.2205900041371491095.davem@davemloft.net> (raw)
In-Reply-To: <20151024145600.GA2937@lkp-hsx03>
From: kbuild test robot <fengguang.wu@intel.com>
Date: Sat, 24 Oct 2015 22:56:01 +0800
> TO: "David S. Miller" <davem@davemloft.net>
> CC: netdev@vger.kernel.org
> CC: Jon Maloy <jon.maloy@ericsson.com>
> CC: Ying Xue <ying.xue@windriver.com>
> CC: tipc-discussion@lists.sourceforge.net
> CC: linux-kernel@vger.kernel.org
>
>
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
Applied.
prev parent reply other threads:[~2015-10-25 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 14:56 [net-next:master 1605/1613] net/tipc/link.c:166:6: sparse: symbol 'link_is_bc_sndlink' was not declared. Should it be static? kbuild test robot
2015-10-24 14:56 ` [RFC PATCH net-next] tipc: link_is_bc_sndlink() can be static kbuild test robot
2015-10-24 18:50 ` Jon Maloy
2015-10-25 13:34 ` 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=20151025.063411.2205900041371491095.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=kbuild-internal@linux.intel.com \
--cc=lkp@eclists.intel.com \
--cc=netdev@vger.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