From: Greg KH <greg@kroah.com>
To: Ben Myers <bpm@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
stable@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 0/6] XFS update for 3.1-stable
Date: Tue, 29 Nov 2011 06:40:18 +0900 [thread overview]
Message-ID: <20111128214018.GB1650@kroah.com> (raw)
In-Reply-To: <20111128165418.GR29840@sgi.com>
On Mon, Nov 28, 2011 at 10:54:18AM -0600, Ben Myers wrote:
> Hey Greg,
>
> On Mon, Nov 28, 2011 at 10:48:29PM +0900, Greg KH wrote:
> > On Mon, Nov 28, 2011 at 06:00:43AM -0500, Christoph Hellwig wrote:
> > > On Wed, Nov 23, 2011 at 03:38:07PM -0600, Ben Myers wrote:
> > > > This is a series of XFS fixes from current mainline which is important for
> > > > 3.1-stable. Note that it is the same patch set that Christoph submitted for
> > > > 3.0-stable, minus the first three patches which are already included in 3.1.
> > > >
> > > > My QA came out ok with these six patches atop 3.1.y. Apologies to those who
> > > > got this mail twice.
> > >
> > > The updates looks good to me.
> >
> > I never saw this series once, can someone please resend them as I don't
> > see them anywhere.
>
> The first time I sent this 3.1.y series you were not on the --to=, which
> is why some people got the series twice but you didn't. Sorry for the
> confusion.
Was stable@vger.kernel.org on the to: line? If so, I should have seen
them through that, but I don't, which is worrysome to me.
> Do you need the series for 3.0 to be resubmitted?
The 3.0 series is already in the last 3.0.11 release, so I don't need
them, I think I need the 3.1 patches, right?
thanks,
greg k-h
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-11-28 21:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 21:38 [PATCH 0/6] XFS update for 3.1-stable Ben Myers
2011-11-23 21:38 ` [PATCH 1/6] xfs: don't serialise direct IO reads on page cache checks Ben Myers
2011-11-23 21:38 ` [PATCH 2/6] xfs: avoid direct I/O write vs buffered I/O race Ben Myers
2011-11-23 21:38 ` [PATCH 3/6] xfs: Return -EIO when xfs_vn_getattr() failed Ben Myers
2011-11-23 21:38 ` [PATCH 4/6] xfs: fix buffer flushing during unmount Ben Myers
2011-11-23 21:38 ` [PATCH 5/6] xfs: Fix possible memory corruption in xfs_readlink Ben Myers
2011-11-23 21:38 ` [PATCH 6/6] xfs: use doalloc flag in xfs_qm_dqattach_one() Ben Myers
2011-11-28 11:00 ` [PATCH 0/6] XFS update for 3.1-stable Christoph Hellwig
2011-11-28 13:48 ` Greg KH
2011-11-28 16:54 ` Ben Myers
2011-11-28 21:40 ` Greg KH [this message]
2011-11-30 18:10 ` XFS update for 3.1-stable (resent) Ben Myers
2011-11-30 18:10 ` [PATCH 1/6] xfs: don't serialise direct IO reads on page cache checks Ben Myers
2011-11-30 18:10 ` [PATCH 2/6] xfs: avoid direct I/O write vs buffered I/O race Ben Myers
2011-11-30 18:10 ` [PATCH 3/6] xfs: Return -EIO when xfs_vn_getattr() failed Ben Myers
2011-11-30 18:10 ` [PATCH 4/6] xfs: fix buffer flushing during unmount Ben Myers
2011-11-30 18:10 ` [PATCH 5/6] xfs: Fix possible memory corruption in xfs_readlink Ben Myers
2011-11-30 18:11 ` [PATCH 6/6] xfs: use doalloc flag in xfs_qm_dqattach_one() Ben Myers
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=20111128214018.GB1650@kroah.com \
--to=greg@kroah.com \
--cc=bpm@sgi.com \
--cc=hch@infradead.org \
--cc=stable@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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