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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 62A28C433EF for ; Fri, 19 Nov 2021 07:08:54 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (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 9E3F561057 for ; Fri, 19 Nov 2021 07:08:53 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 9E3F561057 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kroah.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94.2) (envelope-from ) id 1mny0S-0006PS-Kx; Fri, 19 Nov 2021 02:08:20 -0500 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1mny0Q-0006PE-5E for kernelnewbies@kernelnewbies.org; Fri, 19 Nov 2021 02:08:18 -0500 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B57045C0139; Fri, 19 Nov 2021 02:08:14 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Fri, 19 Nov 2021 02:08:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=cE5Bv9XQdX18nWJNW/u94JBaEy0 cKn/lDHsKq7Xne98=; b=kPq7CGS/0J+SgJZvUm8SHljSyOqy8iAGiiBfW9Uc6t6 dBnaXxajkC+jRDHCqJIUwrFydI1pWVPviFyOdNVbgJ2yoD1ytXXOZ8iQ9Kfg3LXA 7eh8HsUaHM3bFqku4em2kABcBnrosxkaqrJgPI7OR6Qh2RwZvJxKMg///OMCMQb0 6CYNJFwzdhZHG9B7ows3ZD0xk/CBph2glnJ4dZ28yAX6qTpENpfB0uoZotdEaial LqQ//ckhti2vpYaOgJryJMPES33dA3Aq0ZOPtwf950gvAjO3yFkq1hNeAFh91bAQ p8ALLQ4RFO+NtH/+zL1rADjbqkbwmSmZi8sYCwgzsVA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=cE5Bv9 XQdX18nWJNW/u94JBaEy0cKn/lDHsKq7Xne98=; b=iyuTOemTYu5cOrjR9iggZr VHTusaoPKm0sudradrPMWuOcrSrhyqIDa56YBv1Ls4peOCYgWMbeMot1fAgi2O8v iHkrm69GtD3gKVVUDhmB1vEBPiF8qDoQpJcZo0R59BTIEaU7GzGC+gFVKqDOWiJ3 +uapmVHdS5CE8cqGMhvnqXI06pgxoESbPW0Dp2qwMlA+r6e18nIGrNmqqzgM0oyb n/P7V4/QuwehcZasgeFO5ppgriKi2+pcwwo1hT7eEoVswmgw6SjjkL4MskLf5GB0 ngLkD/etQ9qzygE4ydvz4iXQN1MV2BMShl7k+BUoq4WVPqx4izHdXivinVomR6jQ == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrfeejgddutddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepifhrvghgucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheq necuggftrfgrthhtvghrnhepveeuheejgfffgfeivddukedvkedtleelleeghfeljeeiue eggeevueduudekvdetnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomhepghhrvghgsehkrhhorghhrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 19 Nov 2021 02:08:13 -0500 (EST) Date: Fri, 19 Nov 2021 08:08:11 +0100 From: Greg KH To: Ian Pilcher Subject: Re: When reviewers stop responding Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Cc: kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Thu, Nov 18, 2021 at 01:55:41PM -0600, Ian Pilcher wrote: > I am looking for advice on how to proceed when kernel patch reviewers > stop responding to patches. I've been working on a patch series for > several months - sending 3 "RFC" and 8 non-RFC versions, receiving > feedback, and implementing all of the changes that have been requested. > > I sent the last patch series (version 8) on October 9, and resent it on > October 22. I also sent an off-list email to the subsystem maintainer > and the (previously) most active reviewer on November 8. I haven't > received any responses since October 8. > > How should I proceed? As the merge window is now over, please just resend the patches. Remember maintainers can not add anything to their trees usually for the week before, and during the 2 weeks of, the merge window, so that might account for the delay here. Also, just resend because things do get lost. To help out, while waiting, why not review some patches for the same subsystem on the mailing list to provide help for the maintainers? That help can go a long way in making sure your patches are reviewed. good luck! greg k-h _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies