From: Christian Brauner <brauner@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: Christian Brauner <brauner@kernel.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Klara Modin <klarasmodin@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] fat: fix mtime handing in __fat_write_inode
Date: Wed, 18 Oct 2023 13:27:55 +0200 [thread overview]
Message-ID: <20231018-ineinander-gaben-8a939fa0a180@brauner> (raw)
In-Reply-To: <20231018-amtime-v1-1-e066bae97285@kernel.org>
On Wed, 18 Oct 2023 07:15:40 -0400, Jeff Layton wrote:
> Klara reported seeing mangled mtimes when dealing with FAT. Fix the
> braino in the FAT conversion to the new timestamp accessors.
>
>
Thanks for the quick fix!
Folded into "fat: convert to new timestamp accessors" as requested.
---
Applied to the vfs.ctime branch of the vfs/vfs.git tree.
Patches in the vfs.ctime branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.ctime
[1/1] fat: convert to new timestamp accessors
https://git.kernel.org/vfs/vfs/c/07b7351751a8
next prev parent reply other threads:[~2023-10-18 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 11:15 Jeff Layton
2023-10-18 11:27 ` Christian Brauner [this message]
2023-10-18 11:44 ` Klara Modin
2023-10-18 11:55 ` Jeff Layton
2023-10-18 12:03 ` Klara Modin
2023-10-18 12:09 ` Christian Brauner
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=20231018-ineinander-gaben-8a939fa0a180@brauner \
--to=brauner@kernel.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jlayton@kernel.org \
--cc=klarasmodin@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®