Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: John Ogness <john.ogness@linutronix.de>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH] printk: add support for lockless ringbuffer
Date: Mon, 30 Nov 2020 17:34:48 +0100	[thread overview]
Message-ID: <20201130163448.GA20208@vergenet.net> (raw)
In-Reply-To: <20201125222059.6792-1-john.ogness@linutronix.de>

On Wed, Nov 25, 2020 at 11:26:59PM +0106, John Ogness wrote:
> Linux 5.10 moved to a new lockless ringbuffer. The new ringbuffer
> is structured completely different to the previous iterations.
> Add support for retrieving the ringbuffer using vmcoreinfo. The
> new ringbuffer is detected based on the availability of the
> "prb" symbol.
> 
> Signed-off-by: John Ogness <john.ogness@linutronix.de>

Thanks, applied.

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

      reply	other threads:[~2020-11-30 16:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25 22:20 [PATCH] printk: add support for lockless ringbuffer John Ogness
2020-11-30 16:34 ` Simon Horman [this message]

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=20201130163448.GA20208@vergenet.net \
    --to=horms@verge.net.au \
    --cc=john.ogness@linutronix.de \
    --cc=kexec@lists.infradead.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