From: Mike Marshall <hubcap@omnibond.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Mike Marshall <hubcap@omnibond.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [GIT PULL] orangefs: an adjustment and a fix...
Date: Sat, 26 Jun 2021 10:14:40 -0400 [thread overview]
Message-ID: <CAOg9mSR9CM-DV1eqL58HM+m_6fbwgU7KFs3Sab0=A7BOvqoPYQ@mail.gmail.com> (raw)
The following changes since commit 13311e74253fe64329390df80bed3f07314ddd61:
Linux 5.13-rc7 (2021-06-20 15:03:15 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux.git
tags/for-linus-5.13-ofs2
for you to fetch changes up to 1815bba0a5c935d60f0fa180873d9152feb29d09:
orangefs: fix orangefs df output. (2021-06-25 12:00:04 -0400)
----------------------------------------------------------------
Orangefs: and adjustment and a fix
If it is not too late for these... the readahead adjustment
was suggested by Matthew Wilcox and looks like how I should
have written it in the first place... the "df fix" was
suggested by Walt Ligon, some Orangefs users have been complaining
about whacky df output...
----------------------------------------------------------------
Mike Marshall (2):
orangefs: readahead adjustment
orangefs: fix orangefs df output.
fs/orangefs/inode.c | 6 +++---
fs/orangefs/super.c | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
next reply other threads:[~2021-06-26 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 14:14 Mike Marshall [this message]
2021-06-26 17:02 ` [GIT PULL] orangefs: an adjustment and a fix Linus Torvalds
2021-06-27 14:50 ` Mike Marshall
2021-07-06 13:36 Mike Marshall
2021-07-06 19:24 ` pr-tracker-bot
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='CAOg9mSR9CM-DV1eqL58HM+m_6fbwgU7KFs3Sab0=A7BOvqoPYQ@mail.gmail.com' \
--to=hubcap@omnibond.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).