[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190114091014.GB2773@zn.tnic>
Date: Mon, 14 Jan 2019 10:10:14 +0100
From: Borislav Petkov <bp@...en8.de>
To: lijiang <lijiang@...hat.com>
Cc: linux-kernel@...r.kernel.org, kexec@...ts.infradead.org,
tglx@...utronix.de, mingo@...hat.com, x86@...nel.org,
akpm@...ux-foundation.org, bhe@...hat.com, dyoung@...hat.com,
k-hagio@...jp.nec.com, anderson@...hat.com,
linux-doc@...r.kernel.org
Subject: Re: [PATCH 1/2 v6] kdump: add the vmcoreinfo documentation
On Mon, Jan 14, 2019 at 09:52:14AM +0800, lijiang wrote:
> I would like to remove this variable and post again.
No, you should remove the vmcoreinfo export too:
kernel/crash_core.c:398: VMCOREINFO_OSRELEASE(init_uts_ns.name.release);
after making sure userspace is not using it and *then* remove the
documentation.
But you can do that in a separate patch, so that it can be reverted if
trouble.
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists