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=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham 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 61A3AC43381 for ; Wed, 20 Mar 2019 12:42:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2F764213F2 for ; Wed, 20 Mar 2019 12:42:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727540AbfCTMmj (ORCPT ); Wed, 20 Mar 2019 08:42:39 -0400 Received: from ozlabs.org ([203.11.71.1]:48127 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727180AbfCTMmi (ORCPT ); Wed, 20 Mar 2019 08:42:38 -0400 Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 44PV1l1ChVz9sP7; Wed, 20 Mar 2019 23:42:34 +1100 (AEDT) From: Michael Ellerman To: Qian Cai , Christophe Leroy , benh@kernel.crashing.org, paulus@samba.org Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org Subject: Re: [RESEND PATCH v2] powerpc: mute unused-but-set-variable warnings In-Reply-To: References: <20190317220516.92654-1-cai@lca.pw> <1ffdc5ae-2d5f-6c81-3997-0e6c81c67516@c-s.fr> Date: Wed, 20 Mar 2019 23:42:11 +1100 Message-ID: <877ectzpi4.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Qian Cai writes: > On 3/19/19 5:21 AM, Christophe Leroy wrote: >> Is there a reason for resending ? AFAICS, both are identical and still marked >> new in patchwork: >> https://patchwork.ozlabs.org/project/linuxppc-dev/list/?submitter=76055 >> > > "RESEND" because of no maintainer response for more than one week. I don't know who told you to RESEND after a week, but especially at this point in the development cycle a week is *way* too short. And for trivial patches like this I may not get to them for several weeks, I have other problems to fix like time going backward :) In future please check patchwork and then if the patch is still new after several weeks just send a ping in reply to that patch. A full RESEND means I now have two identical patches to deal with in patchwork, which makes more work for me. cheers