Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp722649rwb; Wed, 9 Nov 2022 07:58:05 -0800 (PST) X-Google-Smtp-Source: AMsMyM6M3Yf+gDs+KgIxk/kQ6N87RUABpIxCcYn6l3yMaUsJiRcW0LH2gNCSYpa7eqLQ+pY6PnWb X-Received: by 2002:a17:906:7212:b0:7ad:bd4b:c41f with SMTP id m18-20020a170906721200b007adbd4bc41fmr54412154ejk.659.1668009485032; Wed, 09 Nov 2022 07:58:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1668009485; cv=none; d=google.com; s=arc-20160816; b=jqEsGk0OSB2xZDgDM5M/KdavYsSvF58bNwJ+joTg+I4HDIqW3TIgeswnUhbn9hUCOD ot6Ae9EEDnxv3Yrt0jvp3sGUb9ZFgOArN57f65LR/xTKvPuxy7Il/f/MtbLy+416E+aE t6F+UithD1yk/iYaXrM7t7xNPhsllYNoKB6M6MrcjxiQr/apyUWjG5qFVU2UQ25ZsWIH 5T8gCwCiQ/kBXOoJGtQwSk1T0fE/GarmvqOhKx7KGVP0FkAI2oIJ7ag1Sz+tYTxbBRZD 0lh8dfhdQiUs8Djcjm2zidzlywHPHoprtUAVmTvGg7iW8OqqAlZjuRUDPjsYp60jBGqj lRrA== 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=bZlB38WVbucmOtCsNk10ZN8UEt7RqhzrmrecsrSK3VY=; b=TcZvlk1ep0kjR11iDM9QlpRGGm6gyu6oabYOnKtWL0FDquFNq2eQu1ftjUXrfch4W5 riUxb4zpFxdsyZ/EPlpu3pfA8O/70nMEJKVDPwZDrfJ1+KvS5VWr9NmP39QtxewkJg0B 0NSRAwb0ChCUE7000CBZEC3SWL9PQLyVd7ZoJJbAmKAmrHjHNsvzRhxtUxDqgyhLU+i3 9sMFI1Mc9GrmMJ1E0Hm7O2iDcDQjNDiBYQWaLYaQa1d4W94vudMPXT57P+3IukEYNqFp v32tA1mJ4RBaaT959LH2VSkruNFgtWCDPGRX9YlUCIhMsviE6Vn0ehtFUUHt400LBG46 NpFA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.com header.s=susede1 header.b=meRQrYgw; 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 go13-20020a1709070d8d00b007ae6076db43si16570016ejc.312.2022.11.09.07.57.38; Wed, 09 Nov 2022 07:58:05 -0800 (PST) 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=meRQrYgw; 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 S232010AbiKIPWi (ORCPT + 92 others); Wed, 9 Nov 2022 10:22:38 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54362 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231869AbiKIPWh (ORCPT ); Wed, 9 Nov 2022 10:22:37 -0500 Received: from smtp-out2.suse.de (smtp-out2.suse.de [IPv6:2001:67c:2178:6::1d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B77061D672; Wed, 9 Nov 2022 07:22:36 -0800 (PST) Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id 69F891FA67; Wed, 9 Nov 2022 15:22:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1668007355; 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=bZlB38WVbucmOtCsNk10ZN8UEt7RqhzrmrecsrSK3VY=; b=meRQrYgwqUFj6r9SQkAbbYwkeoHMmGVp6vkuS3hsWI5m6YdLIGK99gYDLCzucznA7nEMs+ hhR827D07eXxbXBT0uqueESB4exkXpOxqbf8QZpQlI9pcYV9oSCqfmrK0rJVV5Zc4D/Omx v5TN2LsvNXwXnFFd9hqqjzRV/x9BRkU= Received: from suse.cz (unknown [10.100.201.202]) (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 4DAB82C143; Wed, 9 Nov 2022 15:22:35 +0000 (UTC) Date: Wed, 9 Nov 2022 16:22:35 +0100 From: Petr Mladek To: John Ogness Cc: Sergey Senozhatsky , Steven Rostedt , Thomas Gleixner , linux-kernel@vger.kernel.org, Greg Kroah-Hartman , linux-fsdevel@vger.kernel.org Subject: Re: [PATCH printk v3 14/40] proc: consoles: document console_lock usage Message-ID: References: <20221107141638.3790965-1-john.ogness@linutronix.de> <20221107141638.3790965-15-john.ogness@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221107141638.3790965-15-john.ogness@linutronix.de> 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 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 Mon 2022-11-07 15:22:12, John Ogness wrote: > The console_lock is held throughout the start/show/stop procedure > to print out device/driver information about all registered > consoles. Since the console_lock is being used for multiple reasons, > explicitly document these reasons. This will be useful when the > console_lock is split into fine-grained locking. > > Signed-off-by: John Ogness Reviewed-by: Petr Mladek Best Regards, Petr