| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 00/15] xfsprogs: libxfs kernel sync to 4.6-for-next |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Wed, 17 Feb 2016 19:16:17 +1100 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20160217075614.GA11432@xxxxxxxxxxxxx> |
| References: | <1455693652-3899-1-git-send-email-david@xxxxxxxxxxxxx> <20160217075614.GA11432@xxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Tue, Feb 16, 2016 at 11:56:14PM -0800, Christoph Hellwig wrote: > The series looks fine modulo the nitpicks I posted. > > But shouldn't the rtinode fixes go into 4.5 as clear bugfixes? None of the changes in those two patches actually affect userspace. These first is a log recovery fix, and the second was to silence a warning in kernel IO submission which doesn't exist in userspace. So apart from syncing up the code, AFAICT there isn't a compelling reason to pull them back into 4.5. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| Previous by Date: | Re: [PATCH 00/15] xfsprogs: libxfs kernel sync to 4.6-for-next, Christoph Hellwig |
|---|---|
| Next by Date: | Re: [PATCH 11/15] xfs: move v1 inode conversion to xfs_inode_from_disk, Dave Chinner |
| Previous by Thread: | Re: [PATCH 00/15] xfsprogs: libxfs kernel sync to 4.6-for-next, Christoph Hellwig |
| Next by Thread: | [PATCH 1/3] xfs: remove xfs_trans_get_block_res, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |