From: Greg KH <greg@kroah.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Brian Foster <bfoster@redhat.com>,
stable@vger.kernel.org, linux-xfs@vger.kernel.org,
Michal Hocko <mhocko@kernel.org>
Subject: Re: [PATCH] xfs: clear delalloc and cache on buffered write failure
Date: Tue, 21 Feb 2017 15:47:16 +0100 [thread overview]
Message-ID: <20170221144716.GA988@kroah.com> (raw)
In-Reply-To: <20170221144000.GA3516@infradead.org>
On Tue, Feb 21, 2017 at 06:40:00AM -0800, Christoph Hellwig wrote:
> On Tue, Feb 21, 2017 at 02:56:39PM +0100, Greg KH wrote:
> > For XFS patches, I need an explicit ack from the maintainer before
> > applying them, as per their instructions in the past...
>
> Brian is one of the most active XFS contributors, you can trust him :)
Heh, ok, but I have been yelled at before for xfs stuff, so I'm a bit
skitish...
I'll queue this up for the next release, after this one that just
started a few hours ago.
thanks,
greg k-h
next prev parent reply other threads:[~2017-02-21 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 13:46 [PATCH] xfs: clear delalloc and cache on buffered write failure Brian Foster
2017-02-21 13:56 ` Greg KH
2017-02-21 14:40 ` Christoph Hellwig
2017-02-21 14:47 ` Greg KH [this message]
2017-02-21 16:33 ` 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=20170221144716.GA988@kroah.com \
--to=greg@kroah.com \
--cc=bfoster@redhat.com \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mhocko@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 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).