All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Rao Shoaib <rao.shoaib@oracle.com>,
	Matthew Wilcox <willy@infradead.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Boqun Feng <boqun.feng@gmail.com>,
	linux-kernel@vger.kernel.org, brouer@redhat.com,
	linux-mm@kvack.org
Subject: Re: [PATCH 1/2] Move kfree_call_rcu() to slab_common.c
Date: Mon, 26 Mar 2018 19:06:13 -0700	[thread overview]
Message-ID: <1522116373.12357.42.camel@perches.com> (raw)
In-Reply-To: <1e8c4382-b97f-659a-59fa-07c71efad970@oracle.com>

On Mon, 2018-03-26 at 18:56 -0700, Rao Shoaib wrote:
> Folks,
> 
> Is anyone working on resolving the check patch issue as I am waiting to 
> resubmit my patch. Will it be fine if I submitted the patch with the 
> original macro as the check is in-correct.

Yes.  Of course.  Anytime a person knows better,
checkpatch output should be ignored.

> I do not speak perl but I can do the process work. If folks think Joe's 
> fix is fine I can submit it and perhaps someone can review it ?

I think it's fine too ;)
Submit away...

  reply	other threads:[~2018-03-27  2:06 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-02 20:11 [PATCH 1/2] Move kfree_call_rcu() to slab_common.c rao.shoaib
2018-01-02 20:11 ` rao.shoaib
2018-01-02 20:11 ` [PATCH 2/2] kfree_rcu() should use the new kfree_bulk() interface for freeing rcu structures rao.shoaib
2018-01-02 20:11   ` rao.shoaib
2018-01-02 22:23 ` [PATCH 1/2] Move kfree_call_rcu() to slab_common.c Matthew Wilcox
2018-01-02 22:23   ` Matthew Wilcox
2018-01-02 22:49   ` Rao Shoaib
2018-01-02 22:49     ` Rao Shoaib
2018-01-04  1:38     ` Boqun Feng
2018-01-04 20:35       ` Rao Shoaib
2018-01-04 20:35         ` Rao Shoaib
2018-01-04 21:27         ` Rao Shoaib
2018-01-04 21:27           ` Rao Shoaib
2018-01-04 21:46           ` Matthew Wilcox
2018-01-04 21:46             ` Matthew Wilcox
2018-01-04 22:18             ` Rao Shoaib
2018-01-04 22:18               ` Rao Shoaib
2018-01-04 23:13               ` Matthew Wilcox
2018-01-04 23:13                 ` Matthew Wilcox
2018-01-04 23:47                 ` Paul E. McKenney
2018-01-04 23:47                   ` Paul E. McKenney
2018-01-05  0:07                   ` Matthew Wilcox
2018-01-05  0:07                     ` Matthew Wilcox
2018-01-05  2:14                     ` Rao Shoaib
2018-01-05  2:14                       ` Rao Shoaib
2018-01-05  6:46                     ` Joe Perches
2018-01-05  6:46                       ` Joe Perches
2018-03-27  1:56                       ` Rao Shoaib
2018-03-27  2:06                         ` Joe Perches [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-02  5:31 [PATCH 0/2] Move kfree_rcu out of rcu code and use kfree_bulk rao.shoaib
2018-04-02  5:31 ` [PATCH 1/2] Move kfree_call_rcu() to slab_common.c rao.shoaib
2018-04-02  7:59   ` kbuild test robot
2018-04-02  7:59     ` kbuild test robot
2018-04-02  9:45   ` kbuild test robot
2018-04-02  9:45     ` kbuild test robot
2018-04-02 15:43     ` Paul E. McKenney
2018-04-03 17:22 [PATCH 0/2] Move kfree_rcu out of rcu code and use kfree_bulk rao.shoaib
2018-04-03 17:22 ` [PATCH 1/2] Move kfree_call_rcu() to slab_common.c rao.shoaib

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=1522116373.12357.42.camel@perches.com \
    --to=joe@perches.com \
    --cc=boqun.feng@gmail.com \
    --cc=brouer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rao.shoaib@oracle.com \
    --cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.