From: Eryu Guan <eguan@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
f@birch.djwong.org, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [ANNOUNCE] xfs-linux: xfs-4.10-misc-fixes-5 updated to ff97f23
Date: Wed, 4 Jan 2017 14:38:59 +0800 [thread overview]
Message-ID: <20170104063859.GP1859@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170104063515.GB14034@birch.djwong.org>
On Tue, Jan 03, 2017 at 10:35:15PM -0800, Darrick J. Wong wrote:
> On Tue, Jan 03, 2017 at 10:11:41PM -0800, Christoph Hellwig wrote:
> > 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
>
> I was wondering if Eryu ever tried his reproducer with this series
> applied? Also, in reminding myself what went on during the v1 review
Not yet, I'll start building & testing them now (based on 4.10-rc2).
Thanks,
Eryu
> thread I also started having a few questions... (see list)
>
> --D
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-01-04 6:39 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
2017-01-04 6:35 ` Darrick J. Wong
2017-01-04 6:38 ` Eryu Guan [this message]
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=20170104063859.GP1859@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=f@birch.djwong.org \
--cc=hch@infradead.org \
--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 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.