[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180501162851.0fceb210@xeon-e3>
Date: Tue, 1 May 2018 16:28:51 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Rahul Lakkireddy <rahul.lakkireddy@...lsio.com>
Cc: netdev@...r.kernel.org, kexec@...ts.infradead.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
davem@...emloft.net, viro@...iv.linux.org.uk,
ebiederm@...ssion.com, akpm@...ux-foundation.org,
torvalds@...ux-foundation.org, ganeshgr@...lsio.com,
nirranjan@...lsio.com, indranil@...lsio.com
Subject: Re: [PATCH net-next v7 1/3] vmcore: add API to collect hardware
dump in second kernel
On Tue, 1 May 2018 23:57:45 +0530
Rahul Lakkireddy <rahul.lakkireddy@...lsio.com> wrote:
> +
> +int vmcore_add_device_dump(struct vmcoredd_data *data)
> +{
> + return __vmcore_add_device_dump(data);
> +}
> +EXPORT_SYMBOL(vmcore_add_device_dump);
> +#endif /* CONFIG_PROC_VMCORE_DEVICE_DUMP
Why the stub wrapper function?
it does nothing.
Powered by blists - more mailing lists