public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Sergey Senozhatsky <senozhatsky@chromium.org>, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, bhe@redhat.com, anton@enomsg.org,
	ccross@android.com, dyoung@redhat.com, feng.tang@intel.com,
	john.ogness@linutronix.de, keescook@chromium.org,
	kernel@gpiccoli.net, kexec@lists.infradead.org,
	rostedt@goodmis.org, tony.luck@intel.com, vgoyal@redhat.com,
	Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH V6] panic: Move panic_print before kmsg dumpers
Date: Wed, 23 Feb 2022 09:30:41 -0300	[thread overview]
Message-ID: <7ea61d75-c924-0ef8-e2a9-463540ce1450@igalia.com> (raw)
In-Reply-To: <YhYdVYYapkaVdvZE@google.com>

On 23/02/2022 08:41, Sergey Senozhatsky wrote:
> On (22/02/15 17:14), Petr Mladek wrote:
>> Makes sense and looks good to me.
>>
>> Reviewed-by: Petr Mladek <pmladek@suse.com>
> 
> FWIW
> 
> Reviewed-by: Sergey Senozhatsky <senozhatsky@chromium.org>

Thanks a lot Sergey, for your review =)

Andrew, do I need to send a V7 with the above tag or this is
incorporated when patch gets into your tree?

Thanks!

  reply	other threads:[~2022-02-23 12:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 14:13 [PATCH V6] panic: Move panic_print before kmsg dumpers Guilherme G. Piccoli
2022-02-15 16:14 ` Petr Mladek
2022-02-23 11:41   ` Sergey Senozhatsky
2022-02-23 12:30     ` Guilherme G. Piccoli [this message]
2022-02-22  1:45 ` Sergey Senozhatsky
2022-02-22 14:08   ` Guilherme G. Piccoli
2022-02-23  1:35     ` Sergey Senozhatsky
2022-02-22  2:06 ` Sergey Senozhatsky
2022-02-22  2:10   ` Sergey Senozhatsky
2022-02-22 14:10   ` Guilherme G. Piccoli
2022-02-23  1:27     ` Sergey Senozhatsky
2022-02-23 13:15       ` Guilherme G. Piccoli
2022-02-24  2:52         ` Sergey Senozhatsky
2022-02-24 14:33       ` Petr Mladek
2022-02-24 14:45         ` Guilherme G. Piccoli
2022-02-25  5:18         ` Sergey Senozhatsky
2022-02-25  5:23           ` Sergey Senozhatsky
2022-02-25 12:16           ` Petr Mladek
2022-02-26  2:23             ` Sergey Senozhatsky
2022-02-28 12:33               ` Guilherme G. Piccoli

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=7ea61d75-c924-0ef8-e2a9-463540ce1450@igalia.com \
    --to=gpiccoli@igalia.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton@enomsg.org \
    --cc=bhe@redhat.com \
    --cc=ccross@android.com \
    --cc=dyoung@redhat.com \
    --cc=feng.tang@intel.com \
    --cc=john.ogness@linutronix.de \
    --cc=keescook@chromium.org \
    --cc=kernel@gpiccoli.net \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=tony.luck@intel.com \
    --cc=vgoyal@redhat.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