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/4] Lustre fixes and cleanups
Date: Sun, 5 Jun 2016 23:28:49 -0400 [thread overview]
Message-ID: <1465183733-3147667-1-git-send-email-green@linuxhacker.ru> (raw)
From: Oleg Drokin <green@linuxhacker.ru>
Here are a few more Lustre fixes and cleanups.
Jinshan Xiong (2):
staging/lustre/lov: calculate file offset correctly
staging/lustre/llite: define per open file cache for ll_cl_context
Oleg Drokin (2):
staging/lustre/osc: Remove ops_temp from osc_page
staging/lustre/osc: Get rid of osc_page_protected()
drivers/staging/lustre/lustre/llite/file.c | 7 +
.../staging/lustre/lustre/llite/llite_internal.h | 11 +-
drivers/staging/lustre/lustre/llite/llite_mmap.c | 5 +
drivers/staging/lustre/lustre/llite/rw.c | 145 +++++++++------------
drivers/staging/lustre/lustre/llite/rw26.c | 17 +--
drivers/staging/lustre/lustre/lov/lov_offset.c | 2 +-
.../staging/lustre/lustre/osc/osc_cl_internal.h | 5 -
drivers/staging/lustre/lustre/osc/osc_page.c | 22 ----
8 files changed, 89 insertions(+), 125 deletions(-)
--
2.7.4
next reply other threads:[~2016-06-06 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 3:28 green [this message]
2016-06-06 3:28 ` [PATCH 1/4] staging/lustre/lov: calculate file offset correctly green
2016-06-06 3:28 ` [PATCH 2/4] staging/lustre/llite: define per open file cache for ll_cl_context green
2016-06-06 3:28 ` [PATCH 3/4] staging/lustre/osc: Remove ops_temp from osc_page green
2016-06-06 3:28 ` [PATCH 4/4] staging/lustre/osc: Get rid of osc_page_protected() 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=1465183733-3147667-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
Powered by JetHome