From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH 1/3] fs: move fs_driver open/close into struct file_operations
Date: Mon, 17 Feb 2025 11:26:50 +0100 [thread overview]
Message-ID: <173978801098.1325040.4745009863210752449.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250214095157.2850839-1-a.fatoum@pengutronix.de>
On Fri, 14 Feb 2025 10:51:55 +0100, Ahmad Fatoum wrote:
> Linux places open and close (called release) in struct file_operations
> and thereby allows implementing them differently depending on inode type.
>
> So far, not being able to do that in barebox didn't bother us much, but
> some kernel file systems depend on the directories to be opened before
> they are iterated through and barebox will start supporting that in the
> later commit.
>
> [...]
Applied, thanks!
[1/3] fs: move fs_driver open/close into struct file_operations
https://git.pengutronix.de/cgit/barebox/commit/?id=e31ca2eea7be (link may not be stable)
[2/3] fs: remove unused members in struct file_operations
https://git.pengutronix.de/cgit/barebox/commit/?id=88798bebccd7 (link may not be stable)
[3/3] fs: drop unused FS_DRIVER_NO_DEV flag
https://git.pengutronix.de/cgit/barebox/commit/?id=a92e661073ff (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-02-17 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 9:51 Ahmad Fatoum
2025-02-14 9:51 ` [PATCH 2/3] fs: remove unused members in " Ahmad Fatoum
2025-02-14 9:51 ` [PATCH 3/3] fs: drop unused FS_DRIVER_NO_DEV flag Ahmad Fatoum
2025-02-17 10:26 ` Sascha Hauer [this message]
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=173978801098.1325040.4745009863210752449.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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