All of lore.kernel.org
 help / color / mirror / Atom feed
From: lijiang <lijiang@redhat.com>
To: Borislav Petkov <bp@alien8.de>
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: Tue, 15 Jan 2019 17:41:16 +0800	[thread overview]
Message-ID: <718e6763-8606-1778-de41-c6bc9f9e8c92@redhat.com> (raw)
In-Reply-To: <20190114091509.GC2773@zn.tnic>

在 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.
> 

WARNING: multiple messages have this Message-ID (diff)
From: lijiang <lijiang@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: k-hagio@ab.jp.nec.com, bhe@redhat.com, linux-doc@vger.kernel.org,
	x86@kernel.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org, mingo@redhat.com,
	anderson@redhat.com, tglx@linutronix.de, dyoung@redhat.com,
	akpm@linux-foundation.org
Subject: Re: [PATCH 1/2 v6] kdump: add the vmcoreinfo documentation
Date: Tue, 15 Jan 2019 17:41:16 +0800	[thread overview]
Message-ID: <718e6763-8606-1778-de41-c6bc9f9e8c92@redhat.com> (raw)
In-Reply-To: <20190114091509.GC2773@zn.tnic>

在 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.
> 

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2019-01-15  9:41 UTC|newest]

Thread overview: 48+ 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 0/2 v6] kdump, vmcoreinfo: " Lianbo Jiang
2019-01-10 12:19 ` [PATCH 1/2 v6] kdump: add the vmcoreinfo documentation Lianbo Jiang
2019-01-10 12:19   ` Lianbo Jiang
2019-01-11 12:33   ` Borislav Petkov
2019-01-11 12:33     ` Borislav Petkov
2019-01-14  1:52     ` lijiang
2019-01-14  1:52       ` lijiang
2019-01-14  9:10       ` Borislav Petkov
2019-01-14  9:10         ` Borislav Petkov
2019-01-14 17:48     ` Kazuhito Hagio
2019-01-14 17:48       ` Kazuhito Hagio
2019-01-14 18:01       ` Borislav Petkov
2019-01-14 18:01         ` Borislav Petkov
2019-01-14 18:58         ` Dave Anderson
2019-01-14 18:58           ` Dave Anderson
2019-01-14 19:21           ` Borislav Petkov
2019-01-14 19:21             ` Borislav Petkov
2019-01-14 19:36             ` Dave Anderson
2019-01-14 19:36               ` Dave Anderson
2019-01-14 19:59               ` Borislav Petkov
2019-01-14 19:59                 ` Borislav Petkov
2019-01-14 20:07                 ` Dave Anderson
2019-01-14 20:07                   ` Dave Anderson
2019-01-14 20:18                   ` Borislav Petkov
2019-01-14 20:18                     ` Borislav Petkov
2019-01-14 20:26                     ` Dave Anderson
2019-01-14 20:26                       ` Dave Anderson
2019-01-14 20:35                       ` Borislav Petkov
2019-01-14 20:35                         ` Borislav Petkov
2019-01-14 20:49                         ` Dave Anderson
2019-01-14 20:49                           ` Dave Anderson
2019-01-15 10:06                           ` Borislav Petkov
2019-01-15 10:06                             ` Borislav Petkov
2019-01-15 11:00                           ` lijiang
2019-01-15 11:00                             ` lijiang
2019-01-11 14:56   ` Borislav Petkov
2019-01-11 14:56     ` Borislav Petkov
2019-01-14  5:30     ` lijiang
2019-01-14  5:30       ` lijiang
2019-01-14  9:15       ` Borislav Petkov
2019-01-14  9:15         ` Borislav Petkov
2019-01-15  9:41         ` lijiang [this message]
2019-01-15  9:41           ` lijiang
2019-01-15 10:09   ` [tip:x86/kdump] kdump: Document kernel data exported in the vmcoreinfo note tip-bot for Lianbo Jiang
2019-01-10 12:19 ` [PATCH 2/2 v6] kdump,vmcoreinfo: Export the value of sme mask to vmcoreinfo Lianbo Jiang
2019-01-10 12:19   ` [PATCH 2/2 v6] kdump, vmcoreinfo: " Lianbo Jiang
2019-01-11 15:15   ` [tip:x86/kdump] x86/kdump: Export the SME " tip-bot for 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=718e6763-8606-1778-de41-c6bc9f9e8c92@redhat.com \
    --to=lijiang@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=anderson@redhat.com \
    --cc=bhe@redhat.com \
    --cc=bp@alien8.de \
    --cc=dyoung@redhat.com \
    --cc=k-hagio@ab.jp.nec.com \
    --cc=kexec@lists.infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.