linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, Bill O'Donnell <billodo@redhat.com>
Subject: Re: [PATCH] isofs: convert isofs to use the new mount API
Date: Thu, 7 Mar 2024 08:58:08 -0600	[thread overview]
Message-ID: <b0cbbb5e-15ec-4e29-a79c-1b5fc18ecc24@redhat.com> (raw)
In-Reply-To: <20240307124225.gm2d4dkscbcg4kt2@quack3>

On 3/7/24 6:42 AM, Jan Kara wrote:
> Hi Eric!
> 
> Thanks for the conversion!
> 
> On Fri 01-03-24 16:56:41, Eric Sandeen wrote:
>> -static int isofs_remount(struct super_block *sb, int *flags, char *data)
>> +static int iso9660_reconfigure(struct fs_context *fc)
> 	      ^^^ Why this renaming? Practically all the function have
> isofs prefix, not iso9660 so I'd prefer to keep it. Similarly with other
> vars defined below. If anything, I'd rename struct iso9660_options to
> struct isofs_options...

I don't remember ;) I was thinking I'd seen both used. Happy to keep everything
as isofs.

>>  {
>> -	sync_filesystem(sb);
>> -	if (!(*flags & SB_RDONLY))
>> +	sync_filesystem(fc->root->d_sb);
>> +	if (!(fc->sb_flags & SB_RDONLY) & SB_RDONLY)
> 					^^^ What's this about?

a braino, oops.

> Otherwise the patch looks good to me!

Will get V2 going shortly. Thanks for the review!

-Eric

> 								Honza


  reply	other threads:[~2024-03-07 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 22:56 [PATCH] isofs: convert isofs to use the new mount API Eric Sandeen
2024-03-07 12:42 ` Jan Kara
2024-03-07 14:58   ` Eric Sandeen [this message]
2024-03-07 18:56   ` [PATCH V2] " Eric Sandeen
2024-03-13 18:03     ` Jan Kara

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=b0cbbb5e-15ec-4e29-a79c-1b5fc18ecc24@redhat.com \
    --to=sandeen@redhat.com \
    --cc=billodo@redhat.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.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).