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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 76419C43334 for ; Tue, 7 Jun 2022 17:19:30 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94.2) (envelope-from ) id 1nycrF-0004um-H9; Tue, 07 Jun 2022 13:19:09 -0400 Received: from mail-oi1-x236.google.com ([2607:f8b0:4864:20::236]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1nycrD-0004uS-54 for kernelnewbies@kernelnewbies.org; Tue, 07 Jun 2022 13:19:07 -0400 Received: by mail-oi1-x236.google.com with SMTP id l81so9297837oif.9 for ; Tue, 07 Jun 2022 10:19:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=ftMqZkkV9Ga+54jA47WdyBk/vqPlh7+PYTVKIsWu2lk=; b=Qaj4nDWm/CBWvyLeLwFxyFYxdaEaOowQnmBu/nby6Lk+s/9j5czYXu4y87TNss5PjI c/budwlKxiIg/Q4I5ut7QEgB8hWVVz++YabUZ7o03V99CQNP7okGGnQRjul8HxeB9DmT FiyccqspHi1N4e0FLBDIi1lr4Mv4DOWYzK8uW65rPEh9md2i6W15rD5kSLrpMuUSROy+ kTDWweuos2Q3cbTZOdakFM8SHoi4uxcjldKrKPanPBZ96x0vpn3BKqcsxELtC9R+UDTu Jfmvi6g0uXD86l/eJNsqpxBeFaieeMiqHzvyP/GxAwSWgVxmEog7cwMLCEmpDG9Zb5ur 2Cmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=ftMqZkkV9Ga+54jA47WdyBk/vqPlh7+PYTVKIsWu2lk=; b=NFa8jVpxw1CHLmtnN7WmAyqZ99jAcVd89+y11j94Uq50IfEAivy740vLpHkVngJAag xVr38vAhtdAL2tLX9giB17T8aUP8bY8Bk4dAUKeuvgP7505FUlrs23tJ/w3xhPhw+bYv VC9ZOMdDAmnr8tM/Tkb97bUbFZUArAtQu/mA62vAVwBenpig+YgT07PUh5b4Z4AMPwYt mJlqdcy4zJNegBmZktTRRy2AHBLsA29h1+GTrekiXi3XeABq8UOUBkAVyu9YZRfHs+H1 /uw2L1tmwWJMMukdehyV1gnhPUJsG9SUFgowR3EmGRmDXTrulZBd8jICpjNvF/JOnnv6 NdKg== X-Gm-Message-State: AOAM5313nQfZWPtCZsxQJFlstXIreiuZahuCkonCbfpdMWr+ogIDUsqR 2wfcOWFUeP/BJZiqzN732+U= X-Google-Smtp-Source: ABdhPJwvWK9gfjtqotPu7wCk8LI22tfoITNMKOCuhK994jXwGg5oopQv1B0CZZYZn/m/nW673kW5Nw== X-Received: by 2002:a05:6808:1403:b0:32b:c9ad:ac60 with SMTP id w3-20020a056808140300b0032bc9adac60mr32233945oiv.277.1654622345120; Tue, 07 Jun 2022 10:19:05 -0700 (PDT) Received: from [172.31.250.1] ([47.184.51.90]) by smtp.gmail.com with ESMTPSA id e28-20020a544f1c000000b0032c18f04800sm10378622oiy.1.2022.06.07.10.19.04 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 07 Jun 2022 10:19:04 -0700 (PDT) Message-ID: <6dc9577f-2628-4f3f-b7f0-f0df8e7cb35b@gmail.com> Date: Tue, 7 Jun 2022 12:19:03 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: When reviewers stop responding Content-Language: en-US To: Greg KH References: From: Ian Pilcher 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: kernelnewbies-bounces@kernelnewbies.org On 11/19/21 01:08, Greg KH wrote: > 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. Well ... 6 more months have passed without any response. During that time I've resent the patch series 3 times. > 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. Unfortunately, I just don't have the knowledge to do that. I am not at all experienced with kernel development, nor do I have any knowledge of interrupt context code or Devicetree, which are the subject of the vast majority of patches to that subsystem. (I don't want to be more specific, because I'm not trying to "name & shame" anyone. I'm sure that the people who work on this particular subsystem are simply overwhelmed.) Is there anything else that I can do? Should I just give up at this point? -- ======================================================================== Google Where SkyNet meets Idiocracy ======================================================================== _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies