From: Waiman Long <waiman.long@hpe.com>
To: Waiman Long <Waiman.Long@hpe.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Jan Kara <jack@suse.com>, Jeff Layton <jlayton@poochiereds.net>,
"J. Bruce Fields" <bfields@fieldses.org>,
Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@linux-foundation.org>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Andi Kleen <andi@firstfloor.org>,
Dave Chinner <dchinner@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
Scott J Norton <scott.norton@hpe.com>,
Douglas Hatch <doug.hatch@hpe.com>
Subject: Re: [RESEND PATCH v7 0/4] vfs: Use per-cpu list for SB's s_inodes list
Date: Tue, 7 Jun 2016 15:35:09 -0400 [thread overview]
Message-ID: <575721ED.7010506@hpe.com> (raw)
In-Reply-To: <575720A6.4000700@hpe.com>
On 06/07/2016 03:29 PM, Waiman Long wrote:
>
>
> Hi, I am resending this patch series as I haven't received any
> feedback to see if further change is needed or is good enough to get
> merged.
>
Sorry, that patch series isn't the latest one. Please ignore it. I am
going to resend the latest one out.
Cheers,
Longman
prev parent reply other threads:[~2016-06-07 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 19:24 [RESEND PATCH v7 0/4] vfs: Use per-cpu list for SB's s_inodes list Waiman Long
2016-06-07 19:24 ` [RESEND PATCH v7 1/4] lib/percpu-list: Per-cpu list with associated per-cpu locks Waiman Long
2016-06-07 19:24 ` [RESEND PATCH v7 2/4] fsnotify: Simplify inode iteration on umount Waiman Long
2016-06-07 19:24 ` [RESEND PATCH v7 3/4] vfs: Remove unnecessary list_for_each_entry_safe() variants Waiman Long
2016-06-07 19:24 ` [RESEND PATCH v7 4/4] vfs: Use per-cpu list for superblock's inode list Waiman Long
2016-06-07 19:29 ` [RESEND PATCH v7 0/4] vfs: Use per-cpu list for SB's s_inodes list Waiman Long
2016-06-07 19:35 ` Waiman Long [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=575721ED.7010506@hpe.com \
--to=waiman.long@hpe.com \
--cc=andi@firstfloor.org \
--cc=bfields@fieldses.org \
--cc=boqun.feng@gmail.com \
--cc=cl@linux-foundation.org \
--cc=dchinner@redhat.com \
--cc=doug.hatch@hpe.com \
--cc=jack@suse.com \
--cc=jlayton@poochiereds.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=scott.norton@hpe.com \
--cc=tj@kernel.org \
--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