[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <718e6763-8606-1778-de41-c6bc9f9e8c92@redhat.com>
Date: Tue, 15 Jan 2019 17:41:16 +0800
From: lijiang <lijiang@...hat.com>
To: Borislav Petkov <bp@...en8.de>
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
在 2019年01月14日 17:15, Borislav Petkov 写道:
> On Mon, Jan 14, 2019 at 01:30:30PM +0800, lijiang wrote:
>> I noticed that the checkpatch was coded in Perl. But i am not familiar with
>> the Perl program language, that would be beyond my ability to do this, i have
>> to learn the Perl program language step by step. :-)
>
> You could give it a try - it is not hard :-)
>
Thank you for encouraging me to do the things.
> And there's no hurry for this, take your time.
>
OK. I would like to put this task in my queue. Once i have free time, i will work
on this issue.
>> Do you mean this one 'KERNEL_IMAGE_SIZE'?
>
> I mean, all those which are unused. Optimally, you should look at the
> tools and see whether they're using those exports and if not, remove
> them. But no hurry here too, take your time.
>
OK. I will check it again, But, basically they are used by Makedumpfile or Crash tools.
> My final goal is to have this up-to-date documentation of what is
> exported and what is used by user tools so that people can look at it
> first before carelessly exporting yet another thing.
>
Agree.
Thanks,
Lianbo
> Thx.
>
Powered by blists - more mailing lists