From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kernel.org ([198.145.29.99]:59460 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726736AbeK3EQp (ORCPT ); Thu, 29 Nov 2018 23:16:45 -0500 Date: Thu, 29 Nov 2018 18:10:38 +0100 From: Greg KH To: Tigran Aivazian Cc: LKML , stable@vger.kernel.org, Tetsuo Handa , syzbot , Andrew Morton , willy@infradead.org, torvalds@linux-foundation.org Subject: Re: [PATCH 4.19 033/110] bfs: add sanity check at bfs_fill_super() Message-ID: <20181129171038.GA4651@kroah.com> References: <20181129135921.231283053@linuxfoundation.org> <20181129135922.602882966@linuxfoundation.org> <20181129160722.GA31919@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org List-ID: On Thu, Nov 29, 2018 at 04:55:20PM +0000, Tigran Aivazian wrote: > On Thu, 29 Nov 2018 at 16:07, Greg KH wrote: > > On Thu, Nov 29, 2018 at 03:23:00PM +0000, Tigran Aivazian wrote: > > > Yes, of course I object to it. > > I can not apply a patch to the stable trees that are not in Linus's tree > > first. So there's nothing I can do here with this. > > Ok, we can wait until my patch propagates into Linus' tree, but I > would have thought it would be a waste of your time to apply a patch > which is waiting to be inevitably superseded by a different one. Your patch has to apply on top of the existing one, so there's not an issue here. And might as well fix it now, as I can never count on a "future" patch getting merged. > I can > see there are 238 PRs at Linus' tree on github and I am very glad that > I looked into one of them --- it contained a long comment explaining > that I should NOT do what I was just about to do, i.e. make a PR > against Linus' tree! :) We do not do kernel development on github :) thanks, greg k-h