Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Daniel Kiper <daniel.kiper@oracle.com>
Cc: olaf@aepfle.de, xen-devel@lists.xensource.com,
	kexec@lists.infradead.org, konrad.wilk@oracle.com
Subject: Re: [PATCH] kexec-tools: Read always one vmcoreinfo file
Date: Fri, 6 Jul 2012 22:49:24 +0900	[thread overview]
Message-ID: <20120706134923.GA8320@verge.net.au> (raw)
In-Reply-To: <20120705121635.GA2007@host-192-168-1-59.local.net-space.pl>

On Thu, Jul 05, 2012 at 02:16:35PM +0200, Daniel Kiper wrote:
> vmcoreinfo file could exists under /sys/kernel (valid on baremetal only)
> and/or under /sys/hypervisor (valid when Xen dom0 is running).
> Read only one of them. It means that only one PT_NOTE will be
> always created. Remove extra code for second PT_NOTE creation.
> 
> Signed-off-by: Daniel Kiper <daniel.kiper@oracle.com>

Thanks, applied.

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

  reply	other threads:[~2012-07-06 13:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-05 12:16 [PATCH] kexec-tools: Read always one vmcoreinfo file Daniel Kiper
2012-07-06 13:49 ` Simon Horman [this message]
2012-07-23 12:56 ` Petr Tesarik
2012-07-23 13:30   ` Petr Tesarik
2012-07-23 20:10     ` Daniel Kiper
2012-07-24  8:18       ` Petr Tesarik
2012-07-24 13:54         ` Daniel Kiper
2012-08-02  3:06           ` Simon Horman
2014-11-13 15:51           ` Petr Tesarik
2014-11-13 17:22             ` Daniel Kiper
2014-11-13 18:14               ` Petr Tesarik
2014-12-19 20:21             ` Daniel Kiper
  -- strict thread matches above, loose matches on Subject: below --
2012-08-02 13:18 Daniel Kiper
2012-08-02 13:27 Daniel Kiper
2012-08-06  8:27 ` Simon Horman
2012-08-06  9:32 Daniel Kiper
2012-09-10 12:06 Daniel Kiper

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=20120706134923.GA8320@verge.net.au \
    --to=horms@verge.net.au \
    --cc=daniel.kiper@oracle.com \
    --cc=kexec@lists.infradead.org \
    --cc=konrad.wilk@oracle.com \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xensource.com \
    /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