From: Dan Williams <dan.j.williams@intel.com>
To: Shiyang Ruan <ruansy.fnst@fujitsu.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Chandan Babu R <chandanbabu@kernel.org>,
Dave Chinner <david@fromorbit.com>, <linux-xfs@vger.kernel.org>,
<nvdimm@lists.linux.dev>, <dan.j.williams@intel.com>
Subject: Re: [PATCH] xfs: drop experimental warning for FSDAX
Date: Fri, 29 Sep 2023 11:34:14 -0700 [thread overview]
Message-ID: <651718a6a6e2c_c558e2943e@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <99279735-2d17-405f-bade-9501a296d817@fujitsu.com>
Shiyang Ruan wrote:
>
>
> 在 2023/9/29 1:13, Darrick J. Wong 写道:
> > On Thu, Sep 28, 2023 at 09:20:52AM -0700, Andrew Morton wrote:
> >> On Thu, 28 Sep 2023 16:44:00 +0800 Shiyang Ruan <ruansy.fnst@fujitsu.com> wrote:
> >>
> >>> But please pick the following patch[1] as well, which fixes failures of
> >>> xfs55[0-2] cases.
> >>>
> >>> [1]
> >>> https://lore.kernel.org/linux-xfs/20230913102942.601271-1-ruansy.fnst@fujitsu.com
> >>
> >> I guess I can take that xfs patch, as it fixes a DAX patch. I hope the xfs team
> >> are watching.
> >>
> >> But
> >>
> >> a) I'm not subscribed to linux-xfs and
> >>
> >> b) the changelog fails to describe the userspace-visible effects of
> >> the bug, so I (and others) are unable to determine which kernel
> >> versions should be patched.
> >>
> >> Please update that changelog and resend?
> >
> > That's a purely xfs patch anyways. The correct maintainer is Chandan,
> > not Andrew.
> >
> > /me notes that post-reorg, patch authors need to ask the release manager
> > (Chandan) directly to merge their patches after they've gone through
> > review. Pull requests of signed tags are encouraged strongly.
> >
> > Shiyang, could you please send Chandan pull requests with /all/ the
> > relevant pmem patches incorporated? I think that's one PR for the
> > "xfs: correct calculation for agend and blockcount" for 6.6; and a
> > second PR with all the non-bugfix stuff (PRE_REMOVE and whatnot) for
> > 6.7.
>
> OK. Though I don't know how to send the PR by email, I have sent a list
> of the patches and added description for each one.
If you want I can create a signed pull request from a git.kernel.org
tree.
Where is that list of patches? I see v15 of preremove.
next prev parent reply other threads:[~2023-09-29 20:16 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 [this message]
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
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=651718a6a6e2c_c558e2943e@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=akpm@linux-foundation.org \
--cc=chandanbabu@kernel.org \
--cc=david@fromorbit.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).