Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp1847599pxb; Sat, 2 Apr 2022 05:53:40 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyZiYHAa5II9qvqMdkK4F4u8K+VJPsruCJxsYhiCDH6XEGQeBvy4C3RqIVd67fESplrAmNz X-Received: by 2002:a63:3fc7:0:b0:398:aad3:3ce1 with SMTP id m190-20020a633fc7000000b00398aad33ce1mr14991472pga.461.1648904020616; Sat, 02 Apr 2022 05:53:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1648904020; cv=none; d=google.com; s=arc-20160816; b=VxFNzFIQT/1LCnHUajQTTV5VdcZCkUFAMRZjwNvdaSGPb8Bkx+eM/ysR7Mc4oqWMpM Gb2ehp6WKwup+u5l2RpszEyE+P7zeeRopFaUhl84IXTqfU4UdYwbLGGP3/cDZBOaGB0Z XOngmvjnPtRKsuDblcfO9rS3QyA0AxJQjqCgBtxcrgFXUOGpybDNyXvnjbfm3Wq2GWca l7L5j9vMGlNSB3j8JVFUumh6JXo8Dpx6+iTQp/SkFws+myUB7cSUUBYy/cahsnxRfpv4 n35okzhoKE+yy2uZXJT/DHDFLK36lbw1g8AKzIE6DL/yr6WZp9JlG0M+1/HWTnVIs4/n skDw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=cP5GUDWML73h6kuyRp+hR2t4fRQn3Mfk1Ujn3Y5Be1o=; b=JMUsUqb4fwCMeaZKtQTDefTKKCNoE/gmJxS91jKySIYr0ShoIHgX7V7RXjRsRTRQ+w L6WsUROr1JJKKm4b7jzj7JRygL7VPcd0ncJLEca/M8fwjgEgKe8nreVT2kXkEaoyE1Zc qGkK/UzeUFE6opCxgk0Dqjb4Ms3WLN4CdKaiySpoukpoROw2sm/vXlt5K9c0TLE86RmC OFo/NQSULl+hlrSAjy2uPY3jfZHD6THxG/l9WVSOrL+qkBlUNGRXNEtFjfvhGHlHCW0m /k0Hnn+CwurNDZFcoCi7g6h7wihGxraVEtqTqGDB1kEClDAn+DMdZNwNOWdIWOcw5gtI GZLA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.com header.s=susede1 header.b=KKxoiQfV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=suse.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b17-20020a63eb51000000b003816043f0e1si4952340pgk.726.2022.04.02.05.53.28; Sat, 02 Apr 2022 05:53:40 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.com header.s=susede1 header.b=KKxoiQfV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=suse.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242811AbiDAMdc (ORCPT + 99 others); Fri, 1 Apr 2022 08:33:32 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54168 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345861AbiDAMdb (ORCPT ); Fri, 1 Apr 2022 08:33:31 -0400 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BC3E8188A0C for ; Fri, 1 Apr 2022 05:31:41 -0700 (PDT) Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id 6BB141FCFF; Fri, 1 Apr 2022 12:31:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1648816300; 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=cP5GUDWML73h6kuyRp+hR2t4fRQn3Mfk1Ujn3Y5Be1o=; b=KKxoiQfV81wR/8BIfKlrq7w9RQxMHjcFkb8pejY9nl24aMLyv6ptR9hCzZsiwlbZjz6I/S /vke2JjzzwO604QKGSqUz4CCOFvCNFBq/+ncfaYUhEDjpeOyqZSS7i8Bo9hUVK/p6Hk4Q4 0w3Wcu/e/xL1gmBMZH/6HpnnSFXrOsM= Received: from suse.cz (unknown [10.100.216.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay2.suse.de (Postfix) with ESMTPS id 4B61BA3B92; Fri, 1 Apr 2022 12:31:40 +0000 (UTC) Date: Fri, 1 Apr 2022 14:31:39 +0200 From: Petr Mladek To: Chris Down Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com Subject: Re: [PATCH] MAINTAINERS: Add printk indexing maintainers on mention of printk_index Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 2022-03-30 15:32:20, Chris Down wrote: > This will primarily catch new and changed printk_index_subsys_emit > calls, but it's also worth catching changes to other printk indexing > infrastructure outside of kernel/printk/index.c. > > This avoids churn due to missing ccs when adding new printk indexes, as > was the case recently for the first round of the XFS printk indexing > patches. > > Signed-off-by: Chris Down > Cc: Petr Mladek Nice trick. I was not aware of that K: entries. I have pushed the patch into printk/linux.git, branch for-5.19. We missed the direct 5.18 train. I will add the commit into a printk pull request for 5.18-rcX if there is any. But I think that it is not worth creating a pull request just with this change. I am going to make sure that you are added into CC in the meantime. I hope that they will add me at least ;-) Best Regards, Petr