From: Andrew Morton <akpm@linux-foundation.org>
To: Baoquan He <bhe@redhat.com>
Cc: willy@infradead.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 0/3] Convert vmcore to use an iov_iter
Date: Mon, 4 Apr 2022 14:34:43 -0700 [thread overview]
Message-ID: <20220404143443.2258fc7e97b45172f7608a77@linux-foundation.org> (raw)
In-Reply-To: <20220402043008.458679-1-bhe@redhat.com>
> On Sat, 2 Apr 2022 12:30:05 +0800 Baoquan He <bhe@redhat.com> wrote:
You were on the patch delivery path, so these patches should have had
your signoff. Documentation/process/submitting-patches.rst explains.
> Copy the description of v3 cover letter from Willy:
> ===
> For some reason several people have been sending bad patches to fix
> compiler warnings in vmcore recently. Here's how it should be done.
> Compile-tested only on x86. As noted in the first patch, s390 should
> take this conversion a bit further, but I'm not inclined to do that
> work myself.
We should tell the S390 maintainers this!
Can you please fix the signoff issue, add the S390 team to Cc and resend?
next prev parent reply other threads:[~2022-04-04 22:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 4:30 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
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 ` Andrew Morton [this message]
2022-04-05 9:04 ` [PATCH v5 0/3] Convert vmcore to use " 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=20220404143443.2258fc7e97b45172f7608a77@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=amit.kachhap@arm.com \
--cc=bhe@redhat.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
all inboxes | Powered by JetHome®