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=-2.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 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 C5E54C54FCB for ; Fri, 24 Apr 2020 22:14:34 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id 90FB620736 for ; Fri, 24 Apr 2020 22:14:34 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="HNHZuPzY" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 90FB620736 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender:Cc:List-Subscribe: List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To: Content-Type:MIME-Version:References:Message-ID:Subject:To:From:Date:Reply-To :Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=++ayavOj86DfKwJJOClEVSfM1NCxWd4Fr2N8x53vAc0=; b=HNHZuPzYJ7/ixFc2K5VMSre9j 3zsNs35tzwKC2Xg/UmZQLp+KPsiuoXG7XQf0Q+5xri+qvISuJOYwXd++EYeIqfmLgEheLQICGgrOg MS+PcHjs2uci1aH+NLdjV7h+zyI7GhMLYbdiKlvKWl11/2HFd8xUbxi0svUGsN2gnVT/QK7k7Oq8h UH3uo+AQl16v/5Ti7czlhFwouYyUcXfaio3jZYJ1Q6hMe3KKf/M+xzPd00l3E+7xtszAT0vdBBBJP hEgwxO5F6pgz/bnuaha20at7FNhcfvWOL37LPR5jgt209V/UY/uJoHBo/Ske5b/Li4Zi9CywGPW1b mbrjpTfVw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jS6ab-0005Xf-S0; Fri, 24 Apr 2020 22:14:29 +0000 Received: from alexa-out-sd-01.qualcomm.com ([199.106.114.38]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1jS6aY-0005Wr-Vn for linux-riscv@lists.infradead.org; Fri, 24 Apr 2020 22:14:28 +0000 Received: from unknown (HELO ironmsg01-sd.qualcomm.com) ([10.53.140.141]) by alexa-out-sd-01.qualcomm.com with ESMTP; 24 Apr 2020 15:14:23 -0700 Received: from gurus-linux.qualcomm.com ([10.46.162.81]) by ironmsg01-sd.qualcomm.com with ESMTP; 24 Apr 2020 15:14:22 -0700 Received: by gurus-linux.qualcomm.com (Postfix, from userid 383780) id 9498C4C8D; Fri, 24 Apr 2020 15:14:22 -0700 (PDT) Date: Fri, 24 Apr 2020 15:14:22 -0700 From: Guru Das Srinagesh To: Lee Jones Subject: Re: [PATCH v13 00/11] Convert PWM period and duty cycle to u64 Message-ID: <20200424221422.GA31118@codeaurora.org> References: <20200423114857.GG3612@dell> <20200423215306.GA8670@codeaurora.org> <20200424064303.GJ3612@dell> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200424064303.GJ3612@dell> User-Agent: Mutt/1.5.21 (2010-09-15) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200424_151427_049509_2BFCCFCE X-CRM114-Status: GOOD ( 14.73 ) X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Kate Stewart , linux-fbdev@vger.kernel.org, David Collins , Liam Girdwood , David Airlie , Michael Turquette , Joonas Lahtinen , Kamil Debski , dri-devel@lists.freedesktop.org, Chris Wilson , Atish Patra , Thierry Reding , linux-riscv@lists.infradead.org, Fabio Estevam , linux-clk@vger.kernel.org, Ville =?utf-8?B?U3lyasOkbMOk?= , Daniel Thompson , Mauro Carvalho Chehab , Alexander Shiyan , Chen-Yu Tsai , NXP Linux Team , Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= , Philipp Zabel , Sascha Hauer , Guenter Roeck , linux-media@vger.kernel.org, linux-pwm@vger.kernel.org, Jean Delvare , Alexandre Torgue , Arnd Bergmann , Bartlomiej Zolnierkiewicz , intel-gfx@lists.freedesktop.org, Maxime Ripard , Mark Brown , Paul Walmsley , Subbaraman Narayanamurthy , Thomas Gleixner , Fabrice Gasnier , Pengutronix Kernel Team , Allison Randal , linux-hwmon@vger.kernel.org, Maxime Coquelin , Richard Fontana , Stephen Boyd , Jingoo Han , linux-kernel@vger.kernel.org, Yash Shah , Palmer Dabbelt , Dan Carpenter , Daniel Vetter , Joe Perches , Shawn Guo Sender: "linux-riscv" Errors-To: linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org On Fri, Apr 24, 2020 at 07:43:03AM +0100, Lee Jones wrote: > A great deal of mailing lists contain numerous protections against > things like flooding and spamming. One of those protections is a > check for "Too many recipients to the message". Most of the time this > simply requires moderator intervention by way of review and approval, > but this ultimately depends on the ML's configuration. > > The first thing to ascertain is why your recipients list is so large. > Have you added every reviewer, subsystem-maintainer, maintainer and > contributor suggested by get-maintainer.pl? If so, consider pruning > that a little. Contributors do not tend to care about subsequent > changes to a file. As someone who receives a lot of patches, I tend > to get fed-up when receiving patches simply because I made a change X > years ago. Stick to listed maintainers/reviewers in the first > instance and see how far that takes you. Thank you for the detailed reply. I did this in the first few patchsets and then when a few patches didn't get any attention, expanded the audience thus. Still, around 50% of the patches in this series remain unreviewed by anyone. > If your recipients list is as succinct as reasonably possible, maybe > just accept that every version isn't going to be archived by every > ML. It's still much more useful for the correct people to have > visibility into the set than for it to be archived multiple times. Thank you, will prune the list and remove past contributors from the Cc-list and add all parties to all patches. Thank you. Guru Das.