From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [ANNOUNCE] xfs-linux: xfs-4.10-misc-fixes-5 updated to ff97f23
Date: Tue, 3 Jan 2017 22:11:41 -0800 [thread overview]
Message-ID: <20170104061141.GA4265@infradead.org> (raw)
In-Reply-To: <20170104054721.GC14031@birch.djwong.org>
On Tue, Jan 03, 2017 at 09:47:21PM -0800, Darrick J. Wong wrote:
> Patches often get missed, so please check if your outstanding
> patches were in this update. If they have not been in this update,
> please resubmit them to linux-xfs@vger.kernel.org so they can be
> picked up in the next update.
>
> I intend to send these four bugfixes to Linus later this week, but
> thought I'd run it by the list first to see if anyone spots anything
> obviously broken.
I'd really like to get the minleft fixes reviewed and to Linus:
http://www.spinics.net/lists/linux-xfs/msg03036.html
next prev parent reply other threads:[~2017-01-04 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 5:47 [ANNOUNCE] xfs-linux: xfs-4.10-misc-fixes-5 updated to ff97f23 Darrick J. Wong
2017-01-04 6:11 ` Christoph Hellwig [this message]
2017-01-04 6:35 ` Darrick J. Wong
2017-01-04 6:38 ` Eryu Guan
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=20170104061141.GA4265@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@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