From: Michael Ellerman <mpe@ellerman.id.au>
To: Ira Weiny <ira.weiny@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] COVER: Remove memcpy_page_flushcache()
Date: Thu, 16 Mar 2023 18:07:31 +1100 [thread overview]
Message-ID: <87lejxmax8.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <64126d113d163_2595222942@iweiny-mobl.notmuch>
Ira Weiny <ira.weiny@intel.com> writes:
> Dave Hansen wrote:
>> On 3/15/23 16:20, Ira Weiny wrote:
>> > Commit 21b56c847753 ("iov_iter: get rid of separate bvec and xarray
>> > callbacks") removed the calls to memcpy_page_flushcache().
>> >
>> > kmap_atomic() is deprecated and used in the x86 version of
>> > memcpy_page_flushcache().
>> >
>> > Remove the unnecessary memcpy_page_flushcache() call from all arch's.
>>
>> Hi Ira,
>>
>> Since the common code user is already gone these three patches seem
>> quite independent. It seems like the right thing to do is have
>> individual arch maintainers cherry pick their arch patch and carry it
>> independently.
>
> Yes.
>
>>
>> Is there a compelling reason to have someone pick up and carry these all
>> together that I'm missing?
>
> No reason. Would you like me to submit them individually?
I'll just grab the powerpc one from the thread, no need to resend.
> Sorry, submitting them separately crossed my mind when I wrote them but I
> kind of forgot as they were all on the same branch and I was waiting for
> after the merge window to submit them.
It's also much easier to run git-send-email HEAD^^^, rather than running
it three separate times, let alone if it's a 20 patch series.
I wonder if we could come up with some convention to indicate that a
series is made up of independent patches, and maintainers are free to
pick them individually - but still sent as a single series.
cheers
next prev parent reply other threads:[~2023-03-16 7:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 23:20 [PATCH 0/3] COVER: Remove memcpy_page_flushcache() Ira Weiny
2023-03-15 23:20 ` [PATCH 1/3] x86, uaccess: " Ira Weiny
2023-03-15 23:20 ` [PATCH 2/3] powerpc: " Ira Weiny
2023-03-15 23:20 ` [PATCH 3/3] arm: uaccess: " Ira Weiny
2023-03-15 23:33 ` [PATCH 0/3] COVER: " Dave Hansen
2023-03-16 1:12 ` Ira Weiny
2023-03-16 7:07 ` Michael Ellerman [this message]
2023-03-16 16:16 ` Ira Weiny
2023-03-17 0:06 ` Michael Ellerman
2023-03-17 14:48 ` Konstantin Ryabitsev
2023-03-27 16:29 ` Will Deacon
2023-04-06 1:09 ` (subset) " Michael Ellerman
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=87lejxmax8.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=ira.weiny@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=npiggin@gmail.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/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