From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A864D1BE88 for ; Thu, 20 Jul 2023 21:42:48 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8F57DC433C8; Thu, 20 Jul 2023 21:42:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1689889368; bh=++9KJC+95Badpi6e4Z9Qi6JrsvpaaCgM0iDxU+I098I=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=oVmzzdHX1ozGOZytAVhUTJfYl3Buw8THkakySyOsv4RCOGIB5ibhd3iuOD4pJPMFZ vapReJq02teqjwMVyVfNlZQ3fPRsz9b0BAMT0zSYQBs4bNVMdG14tQ37AsD2umLWbY 8gNDeFd6abktON2QerTzT/07eQnGb4TUtfmOxUpPdHPLiUXsD1mOOYIU+ibR9JRQMe BhzdDegv2D9xpJRL0NIH2g/SdRRZksFW78Ibr8H+M5IghsnieyhtcSQLtTW6NBgXKT pa0VOJlFlqY5o4m4VbOfZY0VlXISo5YQ2nTzExS6A0gFL+bMZ9PCfWQbCWJoFQC6x7 YYekiguikaBuw== Date: Thu, 20 Jul 2023 14:42:46 -0700 From: Jakub Kicinski To: Edward Cree Cc: corbet@lwn.net, Andrew Lunn , Greg Kroah-Hartman , Krzysztof Kozlowski , Mark Brown , Leon Romanovsky , workflows@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux@leemhuis.info, kvalo@kernel.org, benjamin.poirier@gmail.com Subject: Re: [PATCH docs v3] docs: maintainer: document expectations of small time maintainers Message-ID: <20230720144246.7e3507d1@kernel.org> In-Reply-To: <50164116-9d12-698d-f552-96b52c718749@gmail.com> References: <20230719183225.1827100-1-kuba@kernel.org> <50164116-9d12-698d-f552-96b52c718749@gmail.com> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Thu, 20 Jul 2023 19:23:56 +0100 Edward Cree wrote: > Does this apply even to "checkpatch cleanup patch spam", where other patches > sprayed from the same source (perhaps against other drivers) have already > been nacked as worthless churn? For networking you can check patchwork, if it's already marked as rejected or such - there's no need to respond. > I've generally been assuming I can ignore those, do I need to make > sure to explicitly respond with typically a repeat of what's already > been said elsewhere? Repeating the same thing over and over is sadly a part of being a maintainer, tho.