[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181203064748.GA29882@kroah.com>
Date: Mon, 3 Dec 2018 07:47:48 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Tigran Aivazian <aivazian.tigran@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>, stable@...r.kernel.org,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
syzbot <syzbot+71c6b5d68e91149fc8a4@...kaller.appspotmail.com>,
Andrew Morton <akpm@...ux-foundation.org>, willy@...radead.org,
torvalds@...ux-foundation.org
Subject: Re: [PATCH 4.19.6] BFS: static inode bitmap and extra sanity checking
On Sun, Dec 02, 2018 at 08:21:30PM +0000, Tigran Aivazian wrote:
> On Sun, 2 Dec 2018 at 20:13, Greg KH <gregkh@...uxfoundation.org> wrote:
> > What is the git commit id of this patch in Linus's tree?
>
> In linux-next the commit id is
> d2e6681167c634cfc3558991b59a6f614a31d226 , but it is not in Linus'
> tree (i.e. at github.com/torvalds/linux) yet. It went into Andrew
> Morton's "-mm" tree and then into "linux-next" tree.
Please take a look at:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to get a patch into the stable tree. The patch needs to be in
Linus's tree first, linux-next does not count, sorry.
thanks,
greg k-h
Powered by blists - more mailing lists