From: David Miller <davem@davemloft.net>
To: fengguang.wu@intel.com
Cc: sowmini.varadhan@oracle.com, kbuild-all@01.org,
santosh.shilimkar@oracle.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH linux-next] rds: rds_info_from_znotifier() can be static
Date: Thu, 08 Mar 2018 21:54:15 -0500 (EST) [thread overview]
Message-ID: <20180308.215415.619421604203164749.davem@davemloft.net> (raw)
In-Reply-To: <20180308113729.GA89557@cairo>
From: kbuild test robot <fengguang.wu@intel.com>
Date: Thu, 8 Mar 2018 19:37:30 +0800
> Fixes: 9426bbc6de99 ("rds: use list structure to track information for zerocopy completion notification")
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
Applied.
prev parent reply other threads:[~2018-03-09 2:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 11:37 [linux-next:master 6182/6533] net/rds/message.c:70:27: sparse: symbol 'rds_info_from_znotifier' was not declared. Should it be static? kbuild test robot
2018-03-08 11:37 ` [RFC PATCH linux-next] rds: rds_info_from_znotifier() can be static kbuild test robot
2018-03-09 2:54 ` 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=20180308.215415.619421604203164749.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.com \
--cc=sowmini.varadhan@oracle.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
all inboxes | Powered by JetHome®