| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Backporting the concurrent direct IO write fix to 3.4 |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Wed, 4 Jul 2012 01:54:19 -0400 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, Kerin Millar <kerframil@xxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <20120703231122.GB19223@dastard> |
| References: | <4FF2F41F.5000504@xxxxxxxxx> <20120703160949.GD855@xxxxxxxxxxxxx> <20120703231122.GB19223@dastard> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Wed, Jul 04, 2012 at 09:11:22AM +1000, Dave Chinner wrote: > Is it? So we will have long term support kernels for 3.0.x, 3.2.x > and now 3.4.x? 3.0.x is the long term stable kernel I'm targetting > for backports and there's no way I can really handle more than > that... I remember Greg announced 3.4 to be long term in addition to 3.0 recently. 3.2 only is the Debian release kernel, for which the maintainers offered to maintain it as a formal stable release on kernel.org And yes, it's getting not only confusing but also way to much work for subsystem maintainers. I'm still happy to backport fixes to 3.0, but for more invasive work it's getting a bit too old now. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Backporting the concurrent direct IO write fix to 3.4, Igor M Podlesny |
|---|---|
| Next by Date: | Re: [PATCH 2/2] xfs: do not call xfs_bdstrat_cb in xfs_buf_iodone_callbacks, Christoph Hellwig |
| Previous by Thread: | Re: Backporting the concurrent direct IO write fix to 3.4, Dave Chinner |
| Next by Thread: | [PATCH v2] xfstests: improve test 286 for repeated unwritten/hole extents., Jeff Liu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |