From: Borislav Petkov <bp@alien8.de>
To: lijiang <lijiang@redhat.com>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
akpm@linux-foundation.org, bhe@redhat.com, dyoung@redhat.com,
k-hagio@ab.jp.nec.com, anderson@redhat.com,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/2 v6] kdump: add the vmcoreinfo documentation
Date: Mon, 14 Jan 2019 10:15:10 +0100 [thread overview]
Message-ID: <20190114091509.GC2773@zn.tnic> (raw)
In-Reply-To: <be8fbb64-7748-c7da-55f7-99fe69796a94@redhat.com>
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 :-)
And there's no hurry for this, take your time.
> 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.
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.
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-01-14 9:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 12:19 [PATCH 0/2 v6] kdump,vmcoreinfo: Export the value of sme mask to vmcoreinfo Lianbo Jiang
2019-01-10 12:19 ` [PATCH 1/2 v6] kdump: add the vmcoreinfo documentation Lianbo Jiang
2019-01-11 12:33 ` Borislav Petkov
2019-01-14 1:52 ` lijiang
2019-01-14 9:10 ` Borislav Petkov
2019-01-14 17:48 ` Kazuhito Hagio
2019-01-14 18:01 ` Borislav Petkov
2019-01-14 18:58 ` Dave Anderson
2019-01-14 19:21 ` Borislav Petkov
2019-01-14 19:36 ` Dave Anderson
2019-01-14 19:59 ` Borislav Petkov
2019-01-14 20:07 ` Dave Anderson
2019-01-14 20:18 ` Borislav Petkov
2019-01-14 20:26 ` Dave Anderson
2019-01-14 20:35 ` Borislav Petkov
2019-01-14 20:49 ` Dave Anderson
2019-01-15 10:06 ` Borislav Petkov
2019-01-15 11:00 ` lijiang
2019-01-11 14:56 ` Borislav Petkov
2019-01-14 5:30 ` lijiang
2019-01-14 9:15 ` Borislav Petkov [this message]
2019-01-15 9:41 ` lijiang
2019-01-10 12:19 ` [PATCH 2/2 v6] kdump,vmcoreinfo: Export the value of sme mask to vmcoreinfo Lianbo Jiang
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=20190114091509.GC2773@zn.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=anderson@redhat.com \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=k-hagio@ab.jp.nec.com \
--cc=kexec@lists.infradead.org \
--cc=lijiang@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).