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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no 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 2874FC433DB for ; Wed, 3 Mar 2021 15:43:36 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 8B8B264EE1 for ; Wed, 3 Mar 2021 15:43:35 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8B8B264EE1 Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=suse.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id EF1618D0175; Wed, 3 Mar 2021 10:43:34 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id EA0A88D0157; Wed, 3 Mar 2021 10:43:34 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id D41AB8D0175; Wed, 3 Mar 2021 10:43:34 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0094.hostedemail.com [216.40.44.94]) by kanga.kvack.org (Postfix) with ESMTP id B54E98D0157 for ; Wed, 3 Mar 2021 10:43:34 -0500 (EST) Received: from smtpin25.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id 63FE81730868 for ; Wed, 3 Mar 2021 15:43:34 +0000 (UTC) X-FDA: 77878982748.25.9E81D7A Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by imf06.hostedemail.com (Postfix) with ESMTP id 9EBB0C0007FD for ; Wed, 3 Mar 2021 15:43:31 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1614786205; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ljrynsKsJ5DF/LRlMYU0SVL4erGJQvrwv2Wa8InCBvw=; b=SKo2deU4/61tVEpcohRK//OwAuhtAwEmlQIdbQ2o1uTtNbkZEbqPkgmd+3xrvXqr1/aqut JD/9V0JgGYH6hTc1/b7ry7JwNo7gUdVjxF8Kewbw4XKodOCSHz3sIiwhqOLEE1EBTqiKsB CYDyUN10OFxX2H+e8T4n/S3+CyBC4BY= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 73D5CAD29; Wed, 3 Mar 2021 15:43:25 +0000 (UTC) Date: Wed, 3 Mar 2021 16:43:24 +0100 From: Petr Mladek To: Matthew Wilcox Cc: Yafang Shao , andriy.shevchenko@linux.intel.com, david@redhat.com, linmiaohe@huawei.com, vbabka@suse.cz, cl@linux.com, penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com, akpm@linux-foundation.org, rostedt@goodmis.org, sergey.senozhatsky@gmail.com, joe@perches.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v5 3/3] vsprintf: dump full information of page flags in pGp Message-ID: References: <20210215155141.47432-1-laoar.shao@gmail.com> <20210215155141.47432-4-laoar.shao@gmail.com> <20210222133956.GH2858050@casper.infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210222133956.GH2858050@casper.infradead.org> X-Rspamd-Server: rspam04 X-Rspamd-Queue-Id: 9EBB0C0007FD X-Stat-Signature: ewbwrqs6fck1e33bnh53kfsr7155hg4k Received-SPF: none (suse.com>: No applicable sender policy available) receiver=imf06; identity=mailfrom; envelope-from=""; helo=mx2.suse.de; client-ip=195.135.220.15 X-HE-DKIM-Result: pass/pass X-HE-Tag: 1614786211-815341 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Mon 2021-02-22 13:39:56, Matthew Wilcox wrote: > On Mon, Feb 22, 2021 at 01:38:17PM +0100, Petr Mladek wrote: > > Another question where to push this change. It is pity the we > > finalized it in the middle of the merge window. It has to spend > > at least few days in linux-next. > > > > I would like to hear from Andy before I push it into linux-next. > > There is still theoretical chance to get it into 5.12 when Linus > > prolongs the merge window by one week. it has been delayed by > > a long lasting power outage. > > Usually new code has to be in linux-next by -rc5 or so. This is > definitely too late for 5.12, but it's nice and early for 5.13! OK, I am going to queue it for 5.13 the following week unless anyone speaks against it in the meantime. Best Regards, Petr