public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: akpm@linux-foundation.org
Cc: Baoquan He <bhe@redhat.com>,
	linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	Nick Desaulniers <ndesaulniers@google.com>,
	Dave Young <dyoung@redhat.com>, Kees Cook <keescook@chromium.org>,
	Jiri Olsa <jolsa@kernel.org>, Stephen Boyd <swboyd@chromium.org>,
	Bixuan Cui <cuibixuan@huawei.com>,
	David Vernet <void@manifault.com>,
	Vivek Goyal <vgoyal@redhat.com>,
	Sami Tolvanen <samitolvanen@google.com>
Subject: Re: [PATCH 0/2] Expose kallsyms data in vmcoreinfo note
Date: Mon, 13 Jun 2022 13:39:28 -0700	[thread overview]
Message-ID: <87h74os3gf.fsf@oracle.com> (raw)
In-Reply-To: <Yo2W3mH/5uuAJyw5@MiWiFi-R3L-srv>

Hi Andrew,

Baoquan He <bhe@redhat.com> writes:
> On 05/23/22 at 11:00am, Stephen Brennan wrote:
>> Do you know which tree this patch will go through?
>
> I would like to ask Andrew to help check and pick this if no concern.

Just wanted to check if you would be willing to take a look at this
series and possibly queue it up. I can resend the series directly to you
if you need.

Thanks,
Stephen

  reply	other threads:[~2022-06-13 21:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17  0:05 [PATCH 0/2] Expose kallsyms data in vmcoreinfo note Stephen Brennan
2022-05-17  0:05 ` [PATCH 1/2] kallsyms: Move declarations to internal header Stephen Brennan
2022-05-17  0:05 ` [PATCH 2/2] vmcoreinfo: Include kallsyms symbols Stephen Brennan
2022-05-18 10:19 ` [PATCH 0/2] Expose kallsyms data in vmcoreinfo note Baoquan He
2022-05-23 18:00   ` Stephen Brennan
2022-05-25  2:39     ` Baoquan He
2022-06-13 20:39       ` Stephen Brennan [this message]
2022-06-13 21:26 ` Andrew Morton
2022-06-13 21:59   ` Stephen Brennan
2022-06-13 22:14     ` Andrew Morton
2022-06-13 22:33       ` Stephen Brennan

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=87h74os3gf.fsf@oracle.com \
    --to=stephen.s.brennan@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=cuibixuan@huawei.com \
    --cc=dyoung@redhat.com \
    --cc=jolsa@kernel.org \
    --cc=keescook@chromium.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=samitolvanen@google.com \
    --cc=swboyd@chromium.org \
    --cc=vgoyal@redhat.com \
    --cc=void@manifault.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