From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Byungchul Park <byungchul.park@lge.com>
Cc: peterz@infradead.org, mingo@kernel.org, neilb@suse.de,
viro@zeniv.linux.org.uk, ying.huang@intel.com, oleg@redhat.com,
shli@kernel.org, linux-kernel@vger.kernel.org,
target-devel <target-devel@vger.kernel.org>
Subject: Re: [PATCH v3 4/9] vhost/scsi: Don't reinvent the wheel but use existing llist API
Date: Sat, 18 Feb 2017 21:42:14 -0800 [thread overview]
Message-ID: <1487482934.2958.41.camel@haakon3.risingtidesystems.com> (raw)
In-Reply-To: <1487057190-25191-5-git-send-email-byungchul.park@lge.com>
Hi Byungchul,
On Tue, 2017-02-14 at 16:26 +0900, Byungchul Park wrote:
> Although llist provides proper APIs, they are not used. Make them used.
>
> Signed-off-by: Byungchul Park <byungchul.park@lge.com>
> ---
> drivers/vhost/scsi.c | 11 +++--------
> 1 file changed, 3 insertions(+), 8 deletions(-)
Acked-by: Nicholas Bellinger <nab@linux-iscsi.org>
next prev parent reply other threads:[~2017-02-19 5:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 7:26 [PATCH v3 0/9] " Byungchul Park
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 [this message]
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=1487482934.2958.41.camel@haakon3.risingtidesystems.com \
--to=nab@linux-iscsi.org \
--cc=byungchul.park@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=neilb@suse.de \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=shli@kernel.org \
--cc=target-devel@vger.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
all inboxes | Powered by JetHome®