From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Brennan <stephen.s.brennan@oracle.com>
Cc: Baoquan He <bhe@redhat.com>, Dave Young <dyoung@redhat.com>,
linux-kernel@vger.kernel.org, Vivek Goyal <vgoyal@redhat.com>,
kexec@lists.infradead.org
Subject: Re: [PATCH] vmcoreinfo: add kallsyms_num_syms symbol
Date: Thu, 25 Aug 2022 18:18:13 -0700 [thread overview]
Message-ID: <20220825181813.7a83043882be706bc8391c99@linux-foundation.org> (raw)
In-Reply-To: <a151e3d3-db1d-c3ad-dcd5-3f758b4138ab@oracle.com>
On Thu, 25 Aug 2022 10:27:04 -0700 Stephen Brennan <stephen.s.brennan@oracle.com> wrote:
> I just wanted to check on the status of this. I got your email about it
> being added to mm-hotfixes-unstable, and I do still see it in the quilt
> patches set:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/vmcoreinfo-add-kallsyms_num_syms-symbol.patch
>
> I see the patch in mm-everything-2022-08-15-02-47 but it seems to have
> dropped out in mm-everything-2022-08-17-20-59 and later tags. As a
> result, it no longer shows up in linux-next.
>
> Please excuse me if I'm ignorant of part of your process here, I know
> you handle a huge volume of patches!
Thanks for noticing this - I appear to have messed up a rebase and lost
a batch of hotfixes :(
I readded
mm-hugetlb-avoid-corrupting-page-mapping-in-hugetlb_mcopy_atomic_pte.patch
shmem-update-folio-if-shmem_replace_page-updates-the-page.patch
writeback-avoid-use-after-free-after-removing-device.patch
mailmap-update-guilherme-g-piccolis-email-addresses.patch
vmcoreinfo-add-kallsyms_num_syms-symbol.patch
mm-re-allow-pinning-of-zero-pfns-again.patch
to the hotfixes queue.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2022-08-26 1:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 20:54 [PATCH] vmcoreinfo: add kallsyms_num_syms symbol Stephen Brennan
2022-08-25 17:27 ` Stephen Brennan
2022-08-26 1:18 ` Andrew Morton [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=20220825181813.7a83043882be706bc8391c99@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stephen.s.brennan@oracle.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