From: Baoquan He <bhe@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org, yangtiezhu@loongson.cn,
amit.kachhap@arm.com, hch@lst.de, linux-fsdevel@vger.kernel.org,
viro@zeniv.linux.org.uk
Subject: Re: [PATCH v5 1/3] vmcore: Convert copy_oldmem_page() to take an iov_iter
Date: Sun, 3 Apr 2022 09:25:22 +0800 [thread overview]
Message-ID: <Ykj3gsRD7il4KCLW@MiWiFi-R3L-srv> (raw)
In-Reply-To: <Ykh3FVUFQH0x11Zw@casper.infradead.org>
On 04/02/22 at 05:17pm, Matthew Wilcox wrote:
> On Sat, Apr 02, 2022 at 01:29:31PM +0800, Baoquan He wrote:
> > On 04/02/22 at 12:30pm, Baoquan He wrote:
> >
> > It's odd. I cann't see the content of patches in this series from my
> > mailbox and mail client, but I can see them in lore.kernel.org.
>
> Yes, Red Hat have screwed up their email server again. David Hildenbrand
> already filed a ticket, but you should too so they don't think it's
> just him.
>
> https://lore.kernel.org/linux-mm/6696fb21-090c-37c6-77a7-79423cc9c703@redhat.com/
I see. It could be the same issue. I just filed an internal ticket to
request a fix, thx.
>
> > https://lore.kernel.org/all/20220402043008.458679-1-bhe@redhat.com/T/#u
> >
>
next prev parent reply other threads:[~2022-04-03 1:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 4:30 [PATCH v5 0/3] Convert vmcore to use an iov_iter Baoquan He
2022-04-02 4:30 ` [PATCH v5 1/3] vmcore: Convert copy_oldmem_page() to take " Baoquan He
2022-04-02 5:29 ` Baoquan He
2022-04-02 16:17 ` Matthew Wilcox
2022-04-03 1:25 ` Baoquan He [this message]
2022-04-02 4:30 ` [PATCH v5 2/3] vmcore: Convert __read_vmcore to use " Baoquan He
2022-04-02 4:30 ` [PATCH v5 3/3] vmcore: Convert read_from_oldmem() to take " Baoquan He
2022-04-04 21:34 ` [PATCH v5 0/3] Convert vmcore to use " Andrew Morton
2022-04-05 9:04 ` Baoquan He
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=Ykj3gsRD7il4KCLW@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=amit.kachhap@arm.com \
--cc=hch@lst.de \
--cc=kexec@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=yangtiezhu@loongson.cn \
/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