Received: by 2002:a05:6358:c692:b0:131:369:b2a3 with SMTP id fe18csp4033446rwb; Sun, 30 Jul 2023 23:20:08 -0700 (PDT) X-Google-Smtp-Source: APBJJlGPNbrowzSZsehz6F6wefKzxHJyDQaBm7LnghCYssjN5C3EbLBMQgYvTRM2AWVRDX/sG/XC X-Received: by 2002:a17:90a:dc14:b0:263:3386:9da8 with SMTP id i20-20020a17090adc1400b0026333869da8mr6584270pjv.49.1690784408025; Sun, 30 Jul 2023 23:20:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1690784408; cv=none; d=google.com; s=arc-20160816; b=xZTHKTeUgz+paJYQkkcoDQngBOIHhV6WCT6f+sWyFdFkOvDGep+K7a2DujHmPxZNRD McKd/V7Ce3mVatyJLycDrV+VW/rwvp8sfYIlDaEzwzyVWNgdVija0KGY1RFg81c2d/HB TzIqBkQwhQL2zgsDTVEutpvVZJiVYypNXK8QIjoJKPbmvGwJoMJW2uZaCnzHjcPy4OBX gi5GpVRVAIG0HTsddfE+bHrmw6ptBt4mB886bPoBJA/wC/RmRzFp9W65LfYXJ0wvqhfh 0nzu7aP7bs3tWhzF+Edegewx0uSdhzluWIME4c8IljGSb1HgX/c5TYG6rOHo7WTahFXL kP+w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=hrakyQbVJKLAn9FuENRtvhNz0D+wmRwUSMWXm1emPAo=; fh=jCKEEgUyDcuvBoFgqGpPFxwWixwEhAzXC1lwzfhd2zE=; b=Grx4TooxHSh5GolbnPU3KxNqlNkpNwTgqKhhM4mRjbWpJ6n487sdSzxvsnaZh+YWXN +iXtcxtEPWGvEdn6GAFMq6J/eIQccMMB06XwUSO0ws/DlYSSiiM7Vq/4ZHDkLZYDWWWq ZKnAlxVsX4Bev18a/s0wOjTu0mUYzNjrnSU0PiaT3ZP0aMg8CoT5zP52z5vcnux+6eoD vq5WoL3/zZ4gSXpXAe8+LwINYVSXg/5ds1P9FcX7QVe1uaKLpUMkhUxpq3rTzMbvN701 4rmC1OQiTVNlcLwDnFi8aVxJ++W8kqHKSwUq7Xe0xiM0G6MEzhQsLcXf1VBH04BDzjwD TafQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bt14-20020a17090af00e00b00267f1ec6b98si3316886pjb.127.2023.07.30.23.19.55; Sun, 30 Jul 2023 23:20:08 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229932AbjGaGIA (ORCPT + 99 others); Mon, 31 Jul 2023 02:08:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39446 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230053AbjGaGHz (ORCPT ); Mon, 31 Jul 2023 02:07:55 -0400 Received: from mail.loongson.cn (mail.loongson.cn [114.242.206.163]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id B93F910C6; Sun, 30 Jul 2023 23:07:48 -0700 (PDT) Received: from loongson.cn (unknown [10.20.42.201]) by gateway (Coremail) with SMTP id _____8AxlPCyT8dkq_8MAA--.31150S3; Mon, 31 Jul 2023 14:07:47 +0800 (CST) Received: from [10.20.42.201] (unknown [10.20.42.201]) by localhost.localdomain (Coremail) with SMTP id AQAAf8Dx5sywT8dkJe1BAA--.20979S3; Mon, 31 Jul 2023 14:07:45 +0800 (CST) Subject: Re: [PATCH v13 2/2] spi: loongson: add bus driver for the loongson spi controller To: Mark Brown Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org, Jianmin Lv , wanghongliang@loongson.cn, Liu Peibao , loongson-kernel@lists.loongnix.cn, Andy Shevchenko , zhuyinbo@loongson.cn References: <20230613075834.5219-1-zhuyinbo@loongson.cn> <20230613075834.5219-3-zhuyinbo@loongson.cn> <3822f248-39dc-fb8d-321a-7b6c833cbb3e@loongson.cn> <2264c9bd-76fb-4a99-b655-f4c7bc2a1d45@sirena.org.uk> <8ad55123-fbf2-2b0f-faba-f71bb89c7fb1@loongson.cn> <67b74e69-f660-43e3-831f-47dbe0fea6fa@sirena.org.uk> From: Yinbo Zhu Message-ID: <35724895-6b50-eea1-cc3a-5ad82c501920@loongson.cn> Date: Mon, 31 Jul 2023 14:07:44 +0800 User-Agent: Mozilla/5.0 (X11; Linux loongarch64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <67b74e69-f660-43e3-831f-47dbe0fea6fa@sirena.org.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-CM-TRANSID: AQAAf8Dx5sywT8dkJe1BAA--.20979S3 X-CM-SenderInfo: 52kx5xhqerqz5rrqw2lrqou0/ X-Coremail-Antispam: 1Uk129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7KY7 ZEXasCq-sGcSsGvfJ3UbIjqfuFe4nvWSU5nxnvy29KBjDU0xBIdaVrnUUvcSsGvfC2Kfnx nUUI43ZEXa7xR_UUUUUUUUU== X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 在 2023/7/28 下午8:31, Mark Brown 写道: > On Fri, Jul 28, 2023 at 11:36:48AM +0800, Yinbo Zhu wrote: >> 在 2023/7/27 下午7:37, Mark Brown 写道: >>> On Thu, Jul 27, 2023 at 11:09:16AM +0800, Yinbo Zhu wrote: > >>>> Friendly ping ? > >>> Please don't send content free pings and please allow a reasonable time >>> for review. People get busy, go on holiday, attend conferences and so >>> on so unless there is some reason for urgency (like critical bug fixes) >>> please allow at least a couple of weeks for review. If there have been >>> review comments then people may be waiting for those to be addressed. > >> Sorry, my community experience is poor. How many weeks does the >> community usually take to review ? and this time that I waited for six >> weeks and then ping. > > The delay here is probably fine - the above is a form letter that I send > whenever people ping so it tries to cover all eventualities. How long > to leave things depends a bit on what the change is, an urgent bugfix is > going to be different from a spelling fix in a comment. okay, I got it. > >>> Sending content free pings adds to the mail volume (if they are seen at >>> all) which is often the problem and since they can't be reviewed >>> directly if something has gone wrong you'll have to resend the patches >>> anyway, so sending again is generally a better approach though there are >>> some other maintainers who like them - if in doubt look at how patches >>> for the subsystem are normally handled. > >> Sorry, I don't got it, that free ping usually only needs to be sent to >> the subsystem maintainer? > >> Not recommended to use free ping? or resend the same patch. If the >> patch does not need to be modified, does it require sending the same >> patch ? And the version number remains the same? > > I'm saying it's generally better to ping by resending the patch. > Typically keeping the same version number makes sense when doing that - > people normally say [PATCH RESEND vN] in the subject line. okay, I got it Thanks, Yinbo