From: Christoph Hellwig <hch@lst.de>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
Dave Chinner <david@fromorbit.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Eryu Guan <eguan@redhat.com>,
linux-xfs <linux-xfs@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH v2] xfs: preserve i_rdev when recycling a reclaimable inode
Date: Wed, 14 Mar 2018 16:46:55 +0100 [thread overview]
Message-ID: <20180314154655.GA4937@lst.de> (raw)
In-Reply-To: <CAOQ4uxi0j=S+6zZo8YSzJQ4aSjdK02U2zxuOue7W3NtCrcKmSQ@mail.gmail.com>
On Wed, Mar 14, 2018 at 05:45:40PM +0200, Amir Goldstein wrote:
> I also read between the lines that the responsibility of herding the stable
> patches has shifted from you to Darrick in the last development cycle.
I have no idea if anyone is taking care of the stable tree at the moment,
maybe we'll need a volunteer..
next prev parent reply other threads:[~2018-03-14 15:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 7:44 [PATCH v2] xfs: preserve i_rdev when recycling a reclaimable inode Amir Goldstein
2018-01-26 7:44 ` Christoph Hellwig
2018-01-26 21:44 ` Darrick J. Wong
2018-01-29 11:07 ` Amir Goldstein
2018-01-29 15:50 ` Darrick J. Wong
2018-02-01 0:27 ` Amir Goldstein
2018-02-01 0:29 ` Amir Goldstein
2018-02-01 0:35 ` Darrick J. Wong
2018-03-11 16:08 ` Amir Goldstein
2018-03-11 16:24 ` Greg KH
2018-03-12 16:27 ` Darrick J. Wong
2018-03-12 20:16 ` Amir Goldstein
2018-03-13 6:48 ` Amir Goldstein
2018-03-13 12:46 ` Amir Goldstein
2018-03-13 13:11 ` Christoph Hellwig
2018-03-13 14:33 ` Amir Goldstein
2018-03-13 21:50 ` Dave Chinner
2018-03-14 6:24 ` Amir Goldstein
2018-03-14 12:33 ` Dave Chinner
2018-03-14 12:49 ` Christoph Hellwig
2018-03-14 15:45 ` Amir Goldstein
2018-03-14 15:46 ` Christoph Hellwig [this message]
2018-03-14 16:01 ` Darrick J. Wong
2018-03-19 13:40 ` Greg KH
2018-03-19 14:59 ` Amir Goldstein
2018-03-19 15:19 ` Greg KH
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=20180314154655.GA4937@lst.de \
--to=hch@lst.de \
--cc=amir73il@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=eguan@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-xfs@vger.kernel.org \
--cc=stable@vger.kernel.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.