From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Amir Goldstein <amir73il@gmail.com>,
Murphy Zhou <jencce.kernel@gmail.com>,
fstests <fstests@vger.kernel.org>,
linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] generic/554: test only copy to active swap file
Date: Tue, 18 Jun 2019 08:11:44 -0700 [thread overview]
Message-ID: <20190618151144.GB5387@magnolia> (raw)
In-Reply-To: <20190618150242.GA4576@mit.edu>
On Tue, Jun 18, 2019 at 11:02:42AM -0400, Theodore Ts'o wrote:
> On Tue, Jun 18, 2019 at 12:16:45PM +0300, Amir Goldstein wrote:
> > On Tue, Jun 18, 2019 at 12:02 PM Murphy Zhou <jencce.kernel@gmail.com> wrote:
> > >
> > > Would you mind updating sha1 after it get merged to Linus tree?
> > >
> > > That would be helpful for people tracking this issue.
> > >
> >
> > This is the commit id in linux-next and expected to stay the same
> > when the fix is merged to Linus tree for 5.3.
>
> When I talked to Darrick last week, that was *not* the sense I got
> from him. It's not necessarily guaranteed to be stable just yet...
Darrick hasn't gotten any complaints about the copy-file-range-fixes
branch (which has been in for-next for a week now), so he thinks that
commit id (a31713517dac) should be stable from here on out.
(Note that doesn't guarantee that Linus will pull said branch...)
--D
> - Ted
next prev parent reply other threads:[~2019-06-18 15:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 15:39 [PATCH v2 1/2] generic/553: fix test description Amir Goldstein
2019-06-11 15:39 ` [PATCH v2 2/2] generic/554: test only copy to active swap file Amir Goldstein
2019-06-11 15:41 ` Amir Goldstein
2019-06-11 15:59 ` Theodore Ts'o
2019-06-11 16:07 ` Amir Goldstein
2019-06-18 9:02 ` Murphy Zhou
2019-06-18 9:16 ` Amir Goldstein
2019-06-18 9:36 ` Murphy Zhou
2019-06-18 15:02 ` Theodore Ts'o
2019-06-18 15:11 ` Darrick J. Wong [this message]
2019-06-25 10:29 ` Yang Xu
2019-06-25 10:35 ` Amir Goldstein
2019-06-26 1:18 ` Yang Xu
2019-06-11 15:40 ` [PATCH v2 1/2] generic/553: fix test description Amir Goldstein
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=20190618151144.GB5387@magnolia \
--to=darrick.wong@oracle.com \
--cc=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=jencce.kernel@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
/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).