[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181202200819.GA3932@kroah.com>
Date: Sun, 2 Dec 2018 21:08:19 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Christoph Hellwig <hch@...radead.org>
Cc: Sasha Levin <sashal@...nel.org>,
Amir Goldstein <amir73il@...il.com>,
Dave Chinner <david@...morbit.com>,
stable <stable@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Dave Chinner <dchinner@...hat.com>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-xfs <linux-xfs@...r.kernel.org>,
"Luis R. Chamberlain" <mcgrof@...nel.org>
Subject: Re: XFS patches for stable
On Sun, Dec 02, 2018 at 08:10:16AM -0800, Christoph Hellwig wrote:
> As someone who has done xfs stable backports for a while I really don't
> think the autoselection is helpful at all.
autoselection for xfs patches has been turned off for a while, what
triggered this email thread was a core vfs patch that was backported
that was not obvious it was created by the xfs developers due to a
problem they had found.
> Someone who is vaguely familiar with the code needs to manually select
> the commits and QA them, which takes a fair amount of time, but just
> needs some manual help if it should work ok.
>
> I think we are about ready to have a new xfs stable maintainer lined up
> if everything works well fortunately.
That would be wonderful news.
thanks,
greg k-h
Powered by blists - more mailing lists