All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chandan Babu R <chandanbabu@kernel.org>
To: torvalds@linux-foundation.org
Cc: chandanbabu@kernel.org,dan.j.williams@intel.com,djwong@kernel.org,linux-fsdevel@vger.kernel.org,linux-xfs@vger.kernel.org,ruansy.fnst@fujitsu.com
Subject: [GIT PULL] xfs: Code changes for 6.8
Date: Sat, 02 Mar 2024 18:27:36 +0530	[thread overview]
Message-ID: <87sf184vwb.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)

Hi Linus,

Please pull this branch with changes for xfs for 6.8-rc7. The changes are
limited to just one patch where we drop experimental warning message when
mounting an xfs filesystem on an fsdax device. We now consider xfs on fsdax to
be stable.

I did a test-merge with the main upstream branch as of a few minutes ago and
didn't see any conflicts.  Please let me know if you encounter any
problems.

The following changes since commit d206a76d7d2726f3b096037f2079ce0bd3ba329b:

  Linux 6.8-rc6 (2024-02-25 15:46:06 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-6.8-fixes-4

for you to fetch changes up to 27c86d43bcdb97d00359702713bfff6c006f0d90:

  xfs: drop experimental warning for FSDAX (2024-02-27 09:53:30 +0530)

----------------------------------------------------------------
Changes for 6.8-rc7:

  * Drop experimental warning for FSDAX.

Signed-off-by: Chandan Babu R <chandanbabu@kernel.org>

----------------------------------------------------------------
Shiyang Ruan (1):
      xfs: drop experimental warning for FSDAX

 fs/xfs/xfs_super.c | 1 -
 1 file changed, 1 deletion(-)

-- 
Chandan

             reply	other threads:[~2024-03-02 13:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-02 12:57 Chandan Babu R [this message]
2024-03-02 18:22 ` [GIT PULL] xfs: Code changes for 6.8 pr-tracker-bot

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=87sf184vwb.fsf@debian-BULLSEYE-live-builder-AMD64 \
    --to=chandanbabu@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=djwong@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ruansy.fnst@fujitsu.com \
    --cc=torvalds@linux-foundation.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.