From: "Chuck Lever" <cel@kernel.org>
To: "Christoph Hellwig" <hch@lst.de>
Cc: "Christian Brauner" <brauner@kernel.org>,
NeilBrown <neilb@ownmail.net>, "Jeff Layton" <jlayton@kernel.org>,
"Olga Kornievskaia" <okorniev@redhat.com>,
"Dai Ngo" <dai.ngo@oracle.com>, "Tom Talpey" <tom@talpey.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH v3 1/4] nfsd/blocklayout: always ignore loca_time_modify
Date: Fri, 24 Apr 2026 10:05:04 -0400 [thread overview]
Message-ID: <447b45ba-8b07-451e-8a26-54834ca370ab@app.fastmail.com> (raw)
In-Reply-To: <20260424132203.GA15687@lst.de>
On Fri, Apr 24, 2026, at 9:22 AM, Christoph Hellwig wrote:
> I got two resends of my series without cover letters in my inbox.
> Was this just an accident in sending out some internal tree?
The first resend picked up the wrong patch set, and was a mistake.
The purpose of the second resend was to transfer ownership of this
series to Christian, including fixes and forward porting changes.
The cover letter was not included in the repost because it is not
committed to the new branch.
--
Chuck Lever
next prev parent reply other threads:[~2026-04-24 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 18:18 [PATCH v3 0/4] cleanup block-style layouts exports Chuck Lever
2026-04-23 18:18 ` [PATCH v3 1/4] nfsd/blocklayout: always ignore loca_time_modify Chuck Lever
2026-04-24 13:22 ` Christoph Hellwig
2026-04-24 14:05 ` Chuck Lever [this message]
2026-04-23 18:18 ` [PATCH v3 2/4] exportfs: split out the ops for layout-based block device access Chuck Lever
2026-04-23 18:18 ` [PATCH v3 3/4] exportfs: don't pass struct iattr to ->commit_blocks Chuck Lever
2026-04-23 18:18 ` [PATCH v3 4/4] exportfs,nfsd: rework checking for layout-based block device access support Chuck Lever
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=447b45ba-8b07-451e-8a26-54834ca370ab@app.fastmail.com \
--to=cel@kernel.org \
--cc=brauner@kernel.org \
--cc=dai.ngo@oracle.com \
--cc=hch@lst.de \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@ownmail.net \
--cc=okorniev@redhat.com \
--cc=tom@talpey.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