linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill O'Donnell <bodonnel@redhat.com>
To: Shiyang Ruan <ruansy.fnst@fujitsu.com>
Cc: linux-xfs@vger.kernel.org, nvdimm@lists.linux.dev,
	djwong@kernel.org, chandan.babu@oracle.com,
	dan.j.williams@intel.com
Subject: Re: [PATCH] xfs: drop experimental warning for FSDAX
Date: Thu, 11 Jan 2024 10:59:21 -0600	[thread overview]
Message-ID: <ZaAeaRJnfERwwaP7@redhat.com> (raw)
In-Reply-To: <20230915063854.1784918-1-ruansy.fnst@fujitsu.com>

On Fri, Sep 15, 2023 at 02:38:54PM +0800, Shiyang Ruan wrote:
> FSDAX and reflink can work together now, let's drop this warning.
> 
> Signed-off-by: Shiyang Ruan <ruansy.fnst@fujitsu.com>

Are there any updates on this?
Thanks-
Bill


> ---
>  fs/xfs/xfs_super.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/fs/xfs/xfs_super.c b/fs/xfs/xfs_super.c
> index 1f77014c6e1a..faee773fa026 100644
> --- a/fs/xfs/xfs_super.c
> +++ b/fs/xfs/xfs_super.c
> @@ -371,7 +371,6 @@ xfs_setup_dax_always(
>  		return -EINVAL;
>  	}
>  
> -	xfs_warn(mp, "DAX enabled. Warning: EXPERIMENTAL, use at your own risk");
>  	return 0;
>  
>  disable_dax:
> -- 
> 2.42.0
> 


  parent reply	other threads:[~2024-01-11 16:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  6:38 [PATCH] xfs: drop experimental warning for FSDAX Shiyang Ruan
2023-09-21  8:33 ` Shiyang Ruan
2023-09-26 14:55   ` Darrick J. Wong
2023-09-27  1:18     ` Dave Chinner
2023-09-27  1:46       ` Darrick J. Wong
2023-09-27  3:38         ` Chandan Babu R
2023-09-27  5:17           ` Shiyang Ruan
2023-09-27  6:38             ` Shiyang Ruan
2023-09-27  7:31               ` Chandan Babu R
2023-09-27 15:30                 ` Andrew Morton
2023-09-28  8:44                   ` Shiyang Ruan
2023-09-28 16:20                     ` Andrew Morton
2023-09-28 17:13                       ` Darrick J. Wong
2023-09-29 11:56                         ` Shiyang Ruan
2023-09-29 18:34                           ` Dan Williams
2023-10-02 12:15                             ` Shiyang Ruan
2023-10-02 12:39                               ` Chandan Babu R
2023-10-05  0:08                                 ` Darrick J. Wong
2023-10-05  8:53                                   ` Shiyang Ruan
2023-10-05 16:05                                     ` Darrick J. Wong
2023-10-09 14:14                                       ` Shiyang Ruan
2023-10-09 16:47                                         ` Darrick J. Wong
2023-10-10  3:53                                           ` Shiyang Ruan
2023-10-10 17:51                                             ` Darrick J. Wong
2023-09-29 14:17                       ` Chandan Babu R
2023-09-29 14:35                         ` Eric Sandeen
2023-09-29 15:27                           ` Chandan Babu R
2023-09-29 18:28                           ` Dan Williams
2023-10-04 17:50                             ` Darrick J. Wong
2024-01-11 16:59 ` Bill O'Donnell [this message]
2024-01-12  2:21   ` Darrick J. Wong
2024-02-23  7:28     ` Shiyang Ruan
2024-02-26 16:58       ` Dan Williams
2024-02-27  9:50         ` Shiyang Ruan
2024-02-23 17:32 ` 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=ZaAeaRJnfERwwaP7@redhat.com \
    --to=bodonnel@redhat.com \
    --cc=chandan.babu@oracle.com \
    --cc=dan.j.williams@intel.com \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=ruansy.fnst@fujitsu.com \
    /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).