From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E7228C31E51 for ; Tue, 18 Jun 2019 07:02:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B1D8F20665 for ; Tue, 18 Jun 2019 07:02:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1560841344; bh=2ugJ+4jbEDNf3IaKlqSNtduwn51MkrS5VDiaJCRhmYc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=KjBKEvGdtRheRU6bly2n0tL7ukNFlFvs2tRXgZfPyVQ9tQnH6dvS6G9uadKl8B6+O 3c+Y4LJv55+k7TwC1n06wz0AiGJVBeaOf5DK0qziNeL6cUP2/E1kr3zjGmQLKwW1kr yR2ROoQCReaSI4aF0+f830POYPnrtNlm+4UINX5w= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726088AbfFRHCY (ORCPT ); Tue, 18 Jun 2019 03:02:24 -0400 Received: from mail.kernel.org ([198.145.29.99]:33110 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725829AbfFRHCY (ORCPT ); Tue, 18 Jun 2019 03:02:24 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id F1F6C213F2; Tue, 18 Jun 2019 05:47:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1560836832; bh=2ugJ+4jbEDNf3IaKlqSNtduwn51MkrS5VDiaJCRhmYc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=siWcg5jv7S7enP/dNIGa2avKBd20kFJLLKKmDQOd50TmtgVpdF/ODiH9jSweJauM4 nNPzX4HXmKyOyAqer94mO0tPqUW5raXp9pZaSocIvPrazoQm2xEnZMfxq9gCL/zAqe yPvtYsSUnHMEpRz+yzv515R9CO3+aPiZgySE+QsE= Date: Tue, 18 Jun 2019 07:47:09 +0200 From: Greg Kroah-Hartman To: Gao Xiang Cc: devel@driverdev.osuosl.org, Miao Xie , chao@kernel.org, LKML , weidu.du@huawei.com, Fang Wei , linux-fsdevel@vger.kernel.org, linux-erofs@lists.ozlabs.org Subject: Re: [RFC PATCH 0/8] staging: erofs: decompression inplace approach Message-ID: <20190618054709.GA4271@kroah.com> References: <20190614181619.64905-1-gaoxiang25@huawei.com> <20190617203609.GA22034@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Tue, Jun 18, 2019 at 09:47:08AM +0800, Gao Xiang wrote: > > > On 2019/6/18 4:36, Greg Kroah-Hartman wrote: > > On Sat, Jun 15, 2019 at 02:16:11AM +0800, Gao Xiang wrote: > >> At last, this is RFC patch v1, which means it is not suitable for > >> merging soon... I'm still working on it, testing its stability > >> these days and hope these patches get merged for 5.3 LTS > >> (if 5.3 is a LTS version). > > > > Why would 5.3 be a LTS kernel? > > > > curious as to how you came up with that :) > > My personal thought is about one LTS kernel one year... > Usually 5 versions after the previous kernel...(4.4 -> 4.9 -> 4.14 -> 4.19), > which is not suitable for all historical LTSs...just prepare for 5.3... I try to pick the "last" kernel that is released each year, which sometimes is 5 kernels, sometimes 4, sometimes 6, depending on the release cycle. So odds are it will be 5.4 for the next LTS kernel, but we will not know more until it gets closer to release time. thanks, greg k-h