From: NeilBrown <neilb@suse.com>
To: devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Oleg Drokin <oleg.drokin@intel.com>,
James Simmons <jsimmons@infradead.org>,
Andreas Dilger <andreas.dilger@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lustre Development List <lustre-devel@lists.lustre.org>
Subject: [PATCH 0/3] Three lustre bugfixes
Date: Fri, 23 Feb 2018 09:09:33 +1100 [thread overview]
Message-ID: <151933726925.16436.9827896439357574011.stgit@noble> (raw)
First two patches fix bugs that have been prevented the test suite
from finished for me - now it completes with about 10% of tests
failing.
Third patch fixes a tiny bug I noticed while reviewing another recent
patch to the same file.
Thanks,
NeilBrown
---
NeilBrown (3):
staging: lustre: lov: use correct env in lov_io_data_version_end()
staging: lustre: lmv: correctly iput lmo_root
staging: lustre: lnet/selftest: don't ignore status from lstcon_test_add
drivers/staging/lustre/lnet/selftest/conctl.c | 2 +-
drivers/staging/lustre/lustre/lmv/lmv_obd.c | 2 +-
drivers/staging/lustre/lustre/lov/lov_io.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
--
Signature
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next reply other threads:[~2018-02-22 22:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 22:09 NeilBrown [this message]
2018-02-22 22:09 ` [PATCH 1/3] staging: lustre: lov: use correct env in lov_io_data_version_end() NeilBrown
2018-02-26 14:47 ` James Simmons
2018-02-22 22:09 ` [PATCH 2/3] staging: lustre: lmv: correctly iput lmo_root NeilBrown
2018-02-26 14:48 ` James Simmons
2018-02-22 22:09 ` [PATCH 3/3] staging: lustre: lnet/selftest: don't ignore status from lstcon_test_add NeilBrown
2018-02-26 14:48 ` James Simmons
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=151933726925.16436.9827896439357574011.stgit@noble \
--to=neilb@suse.com \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@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®