From: Paolo Abeni <pabeni@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org, Soheil Hassas Yeganeh <soheil@google.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Carlos Maiolino <cmaiolino@redhat.com>,
Eric Biggers <ebiggers@kernel.org>,
Jacob Keller <jacob.e.keller@intel.com>,
Jens Axboe <axboe@kernel.dk>,
Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v4 RESEND] epoll: use refcount to reduce ep_mutex contention
Date: Wed, 08 Mar 2023 21:34:43 +0100 [thread overview]
Message-ID: <f0c49fb4b682b81d64184d1181bc960728907474.camel@redhat.com> (raw)
In-Reply-To: <20230308104054.84612fbe99e8a57ae57b5ff0@linux-foundation.org>
On Wed, 2023-03-08 at 10:40 -0800, Andrew Morton wrote:
> On Wed, 08 Mar 2023 09:55:31 +0100 Paolo Abeni <pabeni@redhat.com> wrote:
>
> > I have a process question: I understand this is queued for the mm-
> > nonmm-unstable branch. Should I send a v5 with the above comments
> > changes or an incremental patch or something completely different?
>
> Either is OK. If it's a v5 I'll usually queue a delta so people who
> have a;ready reviewed can see what changed. That delta is later
> squashed and I'll use v5's changelog for the whole.
Since even the changelog needs some fixup, I'll send a v5.
Thanks,
Paolo
prev parent reply other threads:[~2023-03-08 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 18:46 [PATCH v4 RESEND] epoll: use refcount to reduce ep_mutex contention Paolo Abeni
2023-03-07 21:17 ` Keller, Jacob E
2023-03-07 21:21 ` Soheil Hassas Yeganeh
2023-03-07 21:30 ` Andrew Morton
2023-03-08 8:55 ` Paolo Abeni
2023-03-08 18:40 ` Andrew Morton
2023-03-08 20:34 ` Paolo Abeni [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=f0c49fb4b682b81d64184d1181bc960728907474.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=cmaiolino@redhat.com \
--cc=ebiggers@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=soheil@google.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).