From: Boqun Feng <boqun.feng@gmail.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: rao.shoaib@oracle.com, brouer@redhat.com, linux-mm@kvack.org
Subject: Re: [PATCH v2 1/1] Move kfree_call_rcu() to slab_common.c
Date: Fri, 22 Dec 2017 10:53:28 +0800 [thread overview]
Message-ID: <20171222025328.GF9516@tardis> (raw)
In-Reply-To: <20171222023846.GE9516@tardis>
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
On Fri, Dec 22, 2017 at 10:38:46AM +0800, Boqun Feng wrote:
> On Thu, Dec 21, 2017 at 05:42:12PM -0800, Paul E. McKenney wrote:
> > On Fri, Dec 22, 2017 at 09:17:04AM +0800, Boqun Feng wrote:
> > > Hi Shoaib,
> > >
> > > On Thu, Dec 21, 2017 at 02:32:50PM -0800, rao.shoaib@oracle.com wrote:
> > > > From: Rao Shoaib <rao.shoaib@oracle.com>
> > > >
> > > > This patch moves kfree_call_rcu() and related macros out of rcu code.
> > > > A new function call_rcu_lazy() is created for calling __call_rcu() with
> > > > the lazy flag. kfree_call_rcu() in the tiny implementation remains unchanged.
> > > >
> > >
> > > Mind to explain why you want to do this in the commit log?
> >
> > I am too close to this one, so I need you guys to hash this out. ;-)
> >
>
> I think simply improving the modularity is OK, but it's better to have
> some words in the commit log ;-)
>
Hmm.. seems like this is first part of the split version for:
https://lkml.kernel.org/r/1513705948-31072-1-git-send-email-rao.shoaib@oracle.com
In that case, Shoaib, I think you'd better send the whole thing as a
proper patchset(which is a set of patches) and write a cover letter.
Feel free to ask questions ;-)
Regards,
Boqun
[...]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-12-22 2:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 22:32 rao.shoaib
2017-12-22 1:17 ` Boqun Feng
2017-12-22 1:42 ` Paul E. McKenney
2017-12-22 2:38 ` Boqun Feng
2017-12-22 2:53 ` Boqun Feng [this message]
2018-01-02 20:18 ` Paul E. McKenney
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=20171222025328.GF9516@tardis \
--to=boqun.feng@gmail.com \
--cc=brouer@redhat.com \
--cc=linux-mm@kvack.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rao.shoaib@oracle.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