From: Byungchul Park <byungchul.park@lge.com>
To: peterz@infradead.org, mingo@kernel.org, neilb@suse.de,
nab@linux-iscsi.org, viro@zeniv.linux.org.uk
Cc: ying.huang@intel.com, oleg@redhat.com, shli@kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/9] Don't reinvent the wheel but use existing llist API
Date: Tue, 14 Feb 2017 16:26:21 +0900 [thread overview]
Message-ID: <1487057190-25191-1-git-send-email-byungchul.park@lge.com> (raw)
Change from v2
- replace for_each(wake_list) with the safe version in scheduler.
- fix a trivial comment in llist.h
Change from v1
- split one patch to several ones, one for each subsystem.
- replace for_each with the safe version where it's necessary.
Byungchul Park (9):
llist: Provide a safe version for llist_for_each
bcache: Don't reinvent the wheel but use existing llist API
raid5: Don't reinvent the wheel but use existing llist API
vhost/scsi: Don't reinvent the wheel but use existing llist API
fput: Don't reinvent the wheel but use existing llist API
namespace.c: Don't reinvent the wheel but use existing llist API
irq_work: Don't reinvent the wheel but use existing llist API
sched: Don't reinvent the wheel but use existing llist API
mm: Don't reinvent the wheel but use existing llist API
drivers/md/bcache/closure.c | 17 +++--------------
drivers/md/raid5.c | 6 ++----
drivers/vhost/scsi.c | 11 +++--------
fs/file_table.c | 12 +++++-------
fs/namespace.c | 12 +++++-------
include/linux/llist.h | 19 +++++++++++++++++++
kernel/irq_work.c | 6 +-----
kernel/sched/core.c | 13 ++-----------
mm/vmalloc.c | 10 ++++------
9 files changed, 44 insertions(+), 62 deletions(-)
--
1.9.1
*** BLURB HERE ***
Byungchul Park (9):
llist: Provide a safe version for llist_for_each
bcache: Don't reinvent the wheel but use existing llist API
raid5: Don't reinvent the wheel but use existing llist API
vhost/scsi: Don't reinvent the wheel but use existing llist API
fput: Don't reinvent the wheel but use existing llist API
namespace.c: Don't reinvent the wheel but use existing llist API
irq_work: Don't reinvent the wheel but use existing llist API
sched: Don't reinvent the wheel but use existing llist API
mm: Don't reinvent the wheel but use existing llist API
drivers/md/bcache/closure.c | 17 +++--------------
drivers/md/raid5.c | 6 ++----
drivers/vhost/scsi.c | 11 +++--------
fs/file_table.c | 12 +++++-------
fs/namespace.c | 12 +++++-------
include/linux/llist.h | 19 +++++++++++++++++++
kernel/irq_work.c | 6 +-----
kernel/sched/core.c | 15 +++------------
mm/vmalloc.c | 10 ++++------
9 files changed, 45 insertions(+), 63 deletions(-)
--
1.9.1
next reply other threads:[~2017-02-14 7:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 7:26 Byungchul Park [this message]
2017-02-14 7:26 ` [PATCH v3 1/9] llist: Provide a safe version for llist_for_each Byungchul Park
2017-02-14 7:45 ` Huang, Ying
2017-03-02 22:59 ` Byungchul Park
2017-03-21 2:53 ` Byungchul Park
2017-02-14 7:26 ` [PATCH v3 2/9] bcache: Don't reinvent the wheel but use existing llist API Byungchul Park
2017-03-02 23:16 ` Byungchul Park
2017-03-05 19:59 ` Jiri Kosina
2017-03-05 22:51 ` Byungchul Park
2017-03-05 22:54 ` Byungchul Park
2017-03-24 0:27 ` Byungchul Park
2017-02-14 7:26 ` [PATCH v3 3/9] raid5: " Byungchul Park
2017-02-16 22:48 ` Shaohua Li
2017-02-14 7:26 ` [PATCH v3 4/9] vhost/scsi: " Byungchul Park
2017-02-19 5:42 ` Nicholas A. Bellinger
2017-02-14 7:26 ` [PATCH v3 5/9] fput: " Byungchul Park
2017-02-14 17:44 ` Oleg Nesterov
2017-03-02 23:09 ` Byungchul Park
2017-02-14 7:26 ` [PATCH v3 6/9] namespace.c: " Byungchul Park
2017-02-14 7:26 ` [PATCH v3 7/9] irq_work: " Byungchul Park
2017-02-14 7:26 ` [PATCH v3 8/9] sched: " Byungchul Park
2017-02-22 5:04 ` Byungchul Park
2017-02-14 7:26 ` [PATCH v3 9/9] mm: " Byungchul Park
2017-05-02 8:03 ` [PATCH v3 0/9] " Byungchul Park
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=1487057190-25191-1-git-send-email-byungchul.park@lge.com \
--to=byungchul.park@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nab@linux-iscsi.org \
--cc=neilb@suse.de \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=shli@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).