From: kbuild test robot <lkp@intel.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
kexec@lists.infradead.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, davem@davemloft.net,
viro@zeniv.linux.org.uk, ebiederm@xmission.com,
stephen@networkplumber.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, ganeshgr@chelsio.com,
nirranjan@chelsio.com, indranil@chelsio.com,
Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Subject: [RFC PATCH] vmcore: __vmcore_add_device_dump() can be static
Date: Sun, 1 Apr 2018 08:32:41 +0800 [thread overview]
Message-ID: <20180401003241.GA77163@lkp-sb-ep06.lkp.intel.com> (raw)
In-Reply-To: <194d1e289b385f2cbd4cb2c2569af93723a9cfb8.1522483891.git.rahul.lakkireddy@chelsio.com>
Fixes: 6bf7e2b7f850 ("vmcore: add API to collect hardware dump in second kernel")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
vmcore.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/proc/vmcore.c b/fs/proc/vmcore.c
index b53698f..fe788dd 100644
--- a/fs/proc/vmcore.c
+++ b/fs/proc/vmcore.c
@@ -1196,7 +1196,7 @@ static void vmcoredd_write_note(const char *name, void *buf, size_t size)
* Write Elf note at the beginning of the buffer to indicate vmcore device
* dump and add the dump to global list.
*/
-int __vmcore_add_device_dump(struct vmcoredd_data *data)
+static int __vmcore_add_device_dump(struct vmcoredd_data *data)
{
size_t note_size, data_size;
struct vmcoredd_node *dump;
next prev parent reply other threads:[~2018-04-01 0:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-31 8:50 [PATCH net-next v3 0/3] kernel: add support to collect hardware logs in crash recovery kernel Rahul Lakkireddy
[not found] ` <cover.1522483890.git.rahul.lakkireddy-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
2018-03-31 8:50 ` [PATCH net-next v3 1/3] vmcore: add API to collect hardware dump in second kernel Rahul Lakkireddy
2018-04-01 0:32 ` kbuild test robot [this message]
2018-04-01 0:32 ` kbuild test robot
2018-03-31 8:50 ` [PATCH net-next v3 2/3] vmcore: append device dumps to vmcore as elf notes Rahul Lakkireddy
2018-03-31 8:50 ` [PATCH net-next v3 3/3] cxgb4: collect hardware dump in second kernel Rahul Lakkireddy
2018-04-01 0:15 ` kbuild test robot
2018-04-01 0:19 ` kbuild test robot
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=20180401003241.GA77163@lkp-sb-ep06.lkp.intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=ganeshgr@chelsio.com \
--cc=indranil@chelsio.com \
--cc=kbuild-all@01.org \
--cc=kexec@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nirranjan@chelsio.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=stephen@networkplumber.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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