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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6A6D3C433F5 for ; Thu, 12 May 2022 09:11:18 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 01CBB6B0074; Thu, 12 May 2022 05:11:18 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id F0F3C6B0075; Thu, 12 May 2022 05:11:17 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id DFCF76B0078; Thu, 12 May 2022 05:11:17 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id D117A6B0074 for ; Thu, 12 May 2022 05:11:17 -0400 (EDT) Received: from smtpin04.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id 925E320C70 for ; Thu, 12 May 2022 09:11:17 +0000 (UTC) X-FDA: 79456522194.04.49C6EE9 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by imf23.hostedemail.com (Postfix) with ESMTP id 05CB51400A5 for ; Thu, 12 May 2022 09:11:02 +0000 (UTC) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 876661F8F4; Thu, 12 May 2022 09:11:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1652346675; 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=fZGQ/vOR7gCkfyiu8i5HUwuHnaGqSWUWPuuLMrnW1vc=; b=LDxw38MEZfmzD+EtDUv1t93Y8YoJWLOHk+Eu4JFrfa9EGfepnpJ9EJHfZ0A65xQkqiJaN2 26TaOHuYxBoiGZPGYK7fdj4HeNMiFiSeP1xJ5yQx4DebxKyQ67/5EhHpigDizkgnhx2NWi Oo7tRoCFfRpQG+GClWS1D5LXPsbUI30= Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 5E5C513A84; Thu, 12 May 2022 09:11:15 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id bQIiFjPPfGIsLQAAMHmgww (envelope-from ); Thu, 12 May 2022 09:11:15 +0000 Date: Thu, 12 May 2022 11:11:13 +0200 From: Michal =?iso-8859-1?Q?Koutn=FD?= To: Ganesan Rajagopal Cc: hannes@cmpxchg.org, mhocko@kernel.org, roman.gushchin@linux.dev, shakeelb@google.com, cgroups@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH v2] mm/memcontrol: Export memcg->watermark via sysfs for v2 memcg Message-ID: <20220512091113.GB5536@blackbody.suse.cz> References: <20220507050916.GA13577@us192.sjc.aristanetworks.com> <20220511174953.GC31592@blackbody.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Authentication-Results: imf23.hostedemail.com; dkim=pass header.d=suse.com header.s=susede1 header.b=LDxw38ME; spf=pass (imf23.hostedemail.com: domain of mkoutny@suse.com designates 195.135.220.29 as permitted sender) smtp.mailfrom=mkoutny@suse.com; dmarc=pass (policy=quarantine) header.from=suse.com X-Rspam-User: X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: 05CB51400A5 X-Stat-Signature: j51i4ppx9repkzaohc3tgarokqwfd364 X-HE-Tag: 1652346662-926754 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 Thu, May 12, 2022 at 08:18:01AM +0530, Ganesan Rajagopal wrote: > Good point. The patch has already been picked up for mm-unstable. Oh, I didn't notice that. > I don't know what's the process in this situation. Should I post a > "[PATCH v3]" with an updated commit message? Or you can send a fixup for folding? (I see this is something new, you better ask Andrew.) Michal