From: Eric Sandeen <sandeen@sandeen.net>
To: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH 3/5] xfs: move xfs_scrub_checkpoint_log to xfs_log_checkpoint for general use
Date: Tue, 1 May 2018 18:04:33 -0500 [thread overview]
Message-ID: <3687ef75-3895-8f60-5342-f90e33c238f1@sandeen.net> (raw)
In-Reply-To: <c57f7f1e-f5f5-56f3-b85c-4c8f6edfba0c@sandeen.net>
On 4/30/18 10:45 AM, Eric Sandeen wrote:
> The upcoming online label patch will require forcing the superblock
> change from the log to the actual on-disk superblock, so move this log
> checkpoint function out for general use.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
self-nak / drop this one, not needed now.
-Eric
next prev parent reply other threads:[~2018-05-01 23:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 15:40 [PATCH 0/5] xfs: add online relabel capabilities Eric Sandeen
2018-04-30 15:42 ` [PATCH 1/5] fs: hoist BTRFS_IOC_[SG]ET_FSLABEL to vfs Eric Sandeen
2018-05-02 14:30 ` Darrick J. Wong
2018-04-30 15:43 ` [PATCH 2/5] xfs: factor out secondary superblock updates Eric Sandeen
2018-05-01 14:17 ` Brian Foster
2018-05-01 14:19 ` Eric Sandeen
2018-05-02 14:29 ` Darrick J. Wong
2018-04-30 15:45 ` [PATCH 3/5] xfs: move xfs_scrub_checkpoint_log to xfs_log_checkpoint for general use Eric Sandeen
2018-05-01 23:04 ` Eric Sandeen [this message]
2018-04-30 15:46 ` [PATCH 4/5] xfs: implement online get/set fs label Eric Sandeen
2018-05-01 14:18 ` Brian Foster
2018-05-01 14:27 ` Eric Sandeen
2018-05-01 14:42 ` Brian Foster
2018-05-01 14:49 ` Darrick J. Wong
2018-05-01 15:01 ` Eric Sandeen
2018-05-01 22:11 ` Dave Chinner
2018-05-01 22:20 ` Eric Sandeen
2018-05-01 23:04 ` [PATCH 4/5 V2] " Eric Sandeen
2018-05-02 10:48 ` Brian Foster
2018-05-02 14:24 ` Darrick J. Wong
2018-05-02 14:28 ` Eric Sandeen
2018-05-02 14:38 ` Darrick J. Wong
2018-05-02 21:57 ` Dave Chinner
2018-04-30 15:48 ` [PATCH 5/5] xfs_io: add label command Eric Sandeen
2018-05-02 14:37 ` Darrick J. Wong
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=3687ef75-3895-8f60-5342-f90e33c238f1@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.