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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id F2ECEC76195 for ; Thu, 23 Mar 2023 12:32:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To: Content-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=q3oFc7HG40RazzjRowLgAFEZAzRcKjLWZeAzXfwUoSw=; b=0hH6H7s06zVlDQ5HyB1t+eKXzo Tmje6IAn/sUmu4g22RRs2ST0oNOsHQJXUN6r88/56VB2G0oGwYA3G0b+jjc6NzWfPJltXEz/OW33p hCRcHw6I8mGXDiqI6z0Ll4lfCFlUnNU/ZzDnF1gWm37l0My1v6YtBNwygc6UGHMUS0vT9lrzCELYw s2MT2VA7YBAiJlBpJQ/16OO3bktRZ5Ssc9c/IENZ4X6zhWRQG7PRtAYqJfEhtODueRXZxAJ6A5kNp TRVnqooT612QXReEDNnWgxFFpECmAOeh7W5UL6b0pwHZrdRNNvhT3SADEH7Hq82CyAkx79rEONW5T 0mkJC57g==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1pfK6y-001v1M-1b; Thu, 23 Mar 2023 12:32:08 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1pfK6u-001v0A-0q; Thu, 23 Mar 2023 12:32:05 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 49E3762672; Thu, 23 Mar 2023 12:32:03 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2FF62C433EF; Thu, 23 Mar 2023 12:31:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1679574722; bh=EYf6786yE/sBEJ5kVxCWKnQjuC3+cnNr9QYBjueYbts=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=J++0vaReFWwPOwPXGP+Po4zvrxhwh5She2/Ec56VQSyU/fB7On301Z7qGfUhVnUyX SdO5C25BT+xlwKrVGf5EnOQLRMO0ivqJ2a1v86lLTJn0ok331QoJwer4z39XS8p4Tv UWf3+tr8QcyH2hsSvavwjncNpjTVFvkGGC9IXuf9140dHvo6FawidhHQRWGdMaF8wQ fcFQXvjQ/lzngUvaOsH6tJBNoNLxkfsvI7wRhhU9EUYNnrTZhsSc7mDc3J2u7PqPVf MF9uFDrtjjga7TBZG1HIgr2H3KboAaLcQttd83XsXeOrQUjR+94n4RpXrBUoAzQqYo rdLJcSSaPByGQ== Date: Thu, 23 Mar 2023 12:31:56 +0000 From: Lee Jones To: Bagas Sanjaya Cc: Linux Documentation , Linux Kernel Mailing List , Linux ARM , Linux MediaTek , Linux LEDs , Jonathan Corbet , Matthias Brugger , AngeloGioacchino Del Regno , Shuah Khan , ChiaEn Wu , ChiYuan Huang Subject: Re: [PATCH 0/3] Documentation fixes for MT6370 RGB Message-ID: <20230323123156.GL2673958@google.com> References: <20230319074903.13075-1-bagasdotme@gmail.com> <2b8667b5-ea54-2ef4-f069-a86acd28ecea@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <2b8667b5-ea54-2ef4-f069-a86acd28ecea@gmail.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230323_053204_336348_599434EF X-CRM114-Status: GOOD ( 17.11 ) X-BeenThere: linux-mediatek@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "Linux-mediatek" Errors-To: linux-mediatek-bounces+linux-mediatek=archiver.kernel.org@lists.infradead.org On Thu, 23 Mar 2023, Bagas Sanjaya wrote: > On 3/19/23 14:49, Bagas Sanjaya wrote: > > kernel test robot recently reported htmldocs warnings on documentation > > for MT6370 RGB LED. So here are the fixes. > > > > Bagas Sanjaya (3): > > Documentation: leds: Add MT6370 doc to the toctree > > Documentation: leds: MT6370: Properly wrap hw_pattern chart > > Documentation: leds: MT6370: Use bullet lists for timing variables > > > > Documentation/leds/index.rst | 1 + > > Documentation/leds/leds-mt6370-rgb.rst | 42 +++++++++++++------------- > > 2 files changed, 22 insertions(+), 21 deletions(-) > > > > > > base-commit: 4ba9df04b7ac66d2d000ed7ae2d8136302d99a57 > > ping a) Don't do that! b) Especually don't do that 4 days after submission! The usual expectation is 2 full weeks before submitting a [RESEND]. Mark Brown says it best: " Please don't send content free pings and please allow a reasonable time for review. People get busy, go on holiday, attend conferences and so on so unless there is some reason for urgency (like critical bug fixes) please allow at least a couple of weeks for review. If there have been review comments then people may be waiting for those to be addressed. Sending content free pings adds to the mail volume (if they are seen at all) which is often the problem and since they can't be reviewed directly if something has gone wrong you'll have to resend the patches anyway, so sending again is generally a better approach though there are some other maintainers who like them - if in doubt look at how patches for the subsystem are normally handled. " -- Lee Jones [李琼斯]