From: green@linuxhacker.ru
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.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>,
Oleg Drokin <green@linuxhacker.ru>
Subject: [PATCH 0/5] Few misc Lustre fixes
Date: Wed, 10 Feb 2016 13:00:17 -0500 [thread overview]
Message-ID: <1455127222-2557752-1-git-send-email-green@linuxhacker.ru> (raw)
From: Oleg Drokin <green@linuxhacker.ru>
This patchset fixes some minor Lustre problems and also
updates the internal version.
Please consider.
Oleg Drokin (5):
staging/lustre/obdecho: Remove always true condition
staging/lustre/obdecho: Better handle invalid create requests
staging/lustre: Adjust import state history output format
staging/lustre: Update internal client version.
staging/lustre: Remove unused LUSTRE_VERSION_ALLOWED_OFFSET define
drivers/staging/lustre/lustre/include/lustre_ver.h | 18 ++++++------------
.../staging/lustre/lustre/obdclass/lprocfs_status.c | 14 +++++++-------
drivers/staging/lustre/lustre/obdecho/echo_client.c | 15 +++++----------
3 files changed, 18 insertions(+), 29 deletions(-)
--
2.1.0
next reply other threads:[~2016-02-10 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 18:00 green [this message]
2016-02-10 18:00 ` [PATCH 1/5] staging/lustre/obdecho: Remove always true condition green
2016-02-10 18:00 ` [PATCH 2/5] staging/lustre/obdecho: Better handle invalid create requests green
2016-02-10 18:00 ` [PATCH 3/5] staging/lustre: Adjust import state history output format green
2016-02-10 18:00 ` [PATCH 4/5] staging/lustre: Update internal client version green
2016-02-10 18:00 ` [PATCH 5/5] staging/lustre: Remove unused LUSTRE_VERSION_ALLOWED_OFFSET define green
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=1455127222-2557752-1-git-send-email-green@linuxhacker.ru \
--to=green@linuxhacker.ru \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.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 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).