linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Eric Sandeen <sandeen@redhat.com>, linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: remove deprecated barrier/nobarrier mount options
Date: Mon, 25 Jun 2018 17:40:38 -0700	[thread overview]
Message-ID: <20180626004038.GB5711@magnolia> (raw)
In-Reply-To: <77374aad-a84d-9cd0-7a41-f5e8e0595dd2@sandeen.net>

On Mon, Jun 25, 2018 at 07:34:20PM -0500, Eric Sandeen wrote:
> On 6/25/18 7:16 PM, Darrick J. Wong wrote:
> > On Mon, Jun 25, 2018 at 07:03:57PM -0500, Eric Sandeen wrote:
> >> The barrier mount options have been no-ops and deprecated since
> >>
> >> 4cf4573 xfs: deprecate barrier/nobarrier mount option
> >>
> >> i.e. kernel 4.10 / December 2016, with a stated deprecation schedule
> >> after v4.15.  Should be fair game to remove them now.
> >>
> >> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> >> ---
> >>  Documentation/filesystems/xfs.txt |    4 ++--
> >>  fs/xfs/xfs_mount.h                |    1 -
> >>  fs/xfs/xfs_super.c                |   34 ++++------------------------------
> >>  3 files changed, 6 insertions(+), 33 deletions(-)
> >>
> >>
> >> diff --git a/Documentation/filesystems/xfs.txt b/Documentation/filesystems/xfs.txt
> >> index 4d9ff0a..07dbd4e 100644
> >> --- a/Documentation/filesystems/xfs.txt
> >> +++ b/Documentation/filesystems/xfs.txt
> >> @@ -223,8 +223,6 @@ Deprecated Mount Options
> >>  
> >>    Name				Removal Schedule
> >>    ----				----------------
> >> -  barrier			no earlier than v4.15
> >> -  nobarrier			no earlier than v4.15
> >>  
> >>  
> >>  Removed Mount Options
> >> @@ -236,6 +234,8 @@ Removed Mount Options
> >>    ihashsize			v4.0
> >>    irixsgid			v4.0
> >>    osyncisdsync/osyncisosync	v4.0
> >> +  barrier			v4.18
> >> +  nobarrier			v4.18
> > 
> > I'm not removing mount options this far into the 4.18 cycle. ;)
> > 
> > 4.19, perhaps?
> 
> Yeah I kinda figured.  Resend V2 later?  Edit on the way in and stash it
> for a while?  V2 now?

v2 now, I'll stuff it in the 4.19 branch when I get around to creating
it......

--D

> 
> -Eric
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-06-26  0:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26  0:03 [PATCH] xfs: remove deprecated barrier/nobarrier mount options Eric Sandeen
2018-06-26  0:16 ` Darrick J. Wong
2018-06-26  0:34   ` Eric Sandeen
2018-06-26  0:40     ` Darrick J. Wong [this message]
2018-06-26  0:43 ` [PATCH 4.19 V2] " Eric Sandeen
2018-06-26 11:23   ` Carlos Maiolino
2018-06-26 14:32   ` Darrick J. Wong
  -- strict thread matches above, loose matches on Subject: below --
2018-07-26 16:01 [PATCH] " Darrick J. Wong
2018-07-26 16:10 ` Eric Sandeen
2018-07-26 16:10 ` 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=20180626004038.GB5711@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=sandeen@sandeen.net \
    /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).