Re: [PATCH 0/2] Tristate moount option comatibility fixup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH 0/2] Tristate moount option comatibility fixup
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 10 Nov 2020 18:35:51 +0000
Cc: linux-xfs@xxxxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, "Theodore Ts'o" <tytso@xxxxxxx>, Andreas Dilger <adilger.kernel@xxxxxxxxx>, "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>, Ira Weiny <ira.weiny@xxxxxxxxx>, Jan Kara <jack@xxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <cover.1604948373.git.msuchanek@suse.de>
References: <cover.1604948373.git.msuchanek@suse.de>

s/moount/mount/

References:
- [PATCH 0/2] Tristate moount option comatibility fixup
  - From: Michal Suchanek

Prev by Date: Re: [PATCH 1/4] xfs: fix brainos in the refcount scrubber's rmap fragment processor
Next by Date: Re: [PATCH 2/9] mkfs: clarify valid "inherit" option values
Previous by thread: Re: [PATCH 0/2] Tristate moount option comatibility fixup
Next by thread: [PATCH AUTOSEL 5.9 45/55] iomap: clean up writeback state logic on writepage error
Index(es):
- Date
- Thread

[Index of Archives] [XFS Filesystem Development (older mail)] [Linux Filesystem Development] [Linux Audio Users] [Yosemite Trails] [Linux Kernel] [Linux RAID] [Linux SCSI]

Powered by Linux