From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f65.google.com ([209.85.221.65]:42332 "EHLO mail-wr1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729618AbeK3EBe (ORCPT ); Thu, 29 Nov 2018 23:01:34 -0500 MIME-Version: 1.0 References: <20181129135921.231283053@linuxfoundation.org> <20181129135922.602882966@linuxfoundation.org> <20181129160722.GA31919@kroah.com> In-Reply-To: <20181129160722.GA31919@kroah.com> From: Tigran Aivazian Date: Thu, 29 Nov 2018 16:55:20 +0000 Message-ID: Subject: Re: [PATCH 4.19 033/110] bfs: add sanity check at bfs_fill_super() To: gregkh@linuxfoundation.org Cc: LKML , stable@vger.kernel.org, Tetsuo Handa , syzbot , Andrew Morton , willy@infradead.org, torvalds@linux-foundation.org Content-Type: text/plain; charset="UTF-8" Sender: stable-owner@vger.kernel.org List-ID: 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. 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! :) And, besides, in the email conversation Linus approved my version of the patch anyway. Kind regards, Tigran