From: Matthew Wilcox <willy@infradead.org>
To: Mike Marshall <hubcap@omnibond.com>
Cc: Martin Brandenburg <martin@omnibond.com>,
devel@lists.orangefs.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 3/9] orangefs: make open_for_read and open_for_write boolean
Date: Wed, 26 Feb 2025 15:50:11 +0000 [thread overview]
Message-ID: <Z784M93R_Job-UOm@casper.infradead.org> (raw)
In-Reply-To: <20250224180529.1916812-4-willy@infradead.org>
On Mon, Feb 24, 2025 at 06:05:21PM +0000, Matthew Wilcox (Oracle) wrote:
> fs/orangefs/file.c | 4 ++--
please ignore vvv all those changes.
> include/linux/mm_types.h | 6 +++---
> include/linux/nfs_page.h | 2 +-
> include/linux/page-flags.h | 6 +++---
I'll take them out locally in case I need to resend
next prev parent reply other threads:[~2025-02-26 15:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 18:05 [PATCH 0/9] Orangefs fixes for 6.15 Matthew Wilcox (Oracle)
2025-02-24 18:05 ` [PATCH 1/9] orangefs: Do not truncate file size Matthew Wilcox (Oracle)
2025-02-24 18:05 ` [PATCH 2/9] orangefs: Move s_kmod_keyword_mask_map to orangefs-debugfs.c Matthew Wilcox (Oracle)
2025-02-24 18:05 ` [PATCH 3/9] orangefs: make open_for_read and open_for_write boolean Matthew Wilcox (Oracle)
2025-02-26 15:50 ` Matthew Wilcox [this message]
2025-02-24 18:05 ` [PATCH 4/9] orangefs: Remove orangefs_writepage() Matthew Wilcox (Oracle)
2025-02-24 18:05 ` [PATCH 5/9] orangefs: Convert orangefs_writepage_locked() to take a folio Matthew Wilcox (Oracle)
2025-02-24 18:05 ` [PATCH 6/9] orangefs: Pass mapping to orangefs_writepages_work() Matthew Wilcox (Oracle)
2025-02-24 18:05 ` [PATCH 7/9] orangefs: Unify error & success paths in orangefs_writepages_work() Matthew Wilcox (Oracle)
2025-02-24 18:05 ` [PATCH 8/9] orangefs: Simplify bvec setup " Matthew Wilcox (Oracle)
2025-02-24 18:05 ` [PATCH 9/9] orangefs: Convert orangefs_writepages to contain an array of folios Matthew Wilcox (Oracle)
2025-02-27 20:18 ` [PATCH 0/9] Orangefs fixes for 6.15 Mike Marshall
2025-03-01 14:34 ` Mike Marshall
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=Z784M93R_Job-UOm@casper.infradead.org \
--to=willy@infradead.org \
--cc=devel@lists.orangefs.org \
--cc=hubcap@omnibond.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=martin@omnibond.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;
as well as URLs for NNTP newsgroup(s).