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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E5ED0C761A6 for ; Thu, 30 Mar 2023 14:15:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231929AbjC3OPh (ORCPT ); Thu, 30 Mar 2023 10:15:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39284 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231805AbjC3OPg (ORCPT ); Thu, 30 Mar 2023 10:15:36 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B392D5FE5; Thu, 30 Mar 2023 07:15:34 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 67597B828FF; Thu, 30 Mar 2023 14:15:33 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D04B9C433EF; Thu, 30 Mar 2023 14:15:28 +0000 (UTC) Date: Thu, 30 Mar 2023 10:15:26 -0400 From: Steven Rostedt To: Borislav Petkov Cc: Donglin Peng , mhiramat@kernel.org, linux@armlinux.org.uk, mark.rutland@arm.com, will@kernel.org, catalin.marinas@arm.com, rmk+kernel@armlinux.org.uk, palmer@dabbelt.com, paul.walmsley@sifive.com, aou@eecs.berkeley.edu, tglx@linutronix.de, dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com, chenhuacai@kernel.org, zhangqing@loongson.cn, kernel@xen0n.name, mingo@redhat.com, peterz@infradead.org, xiehuan09@gmail.com, dinghui@sangfor.com.cn, huangcun@sangfor.com.cn, dolinux.peng@gmail.com, linux-trace-kernel@vger.kernel.org, loongarch@lists.linux.dev, linux-riscv@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v9 0/8] function_graph: Support recording and printing the return value of function Message-ID: <20230330101526.2c862a42@gandalf.local.home> In-Reply-To: <20230330135948.GCZCWV1O/IjsxsBmN8@fat_crate.local> References: <20230330135948.GCZCWV1O/IjsxsBmN8@fat_crate.local> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-trace-kernel@vger.kernel.org On Thu, 30 Mar 2023 15:59:48 +0200 Borislav Petkov wrote: > Please control your spamming: > > From: Documentation/process/submitting-patches.rst > > Don't get discouraged - or impatient > ------------------------------------ > > After you have submitted your change, be patient and wait. Reviewers are > busy people and may not get to your patch right away. > > Once upon a time, patches used to disappear into the void without comment, > but the development process works more smoothly than that now. You should > receive comments within a week or so; if that does not happen, make sure > that you have sent your patches to the right place. Wait for a minimum of > ^^^^^^^^^^^^^^^^^^^^^ > > one week before resubmitting or pinging reviewers - possibly longer during > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > busy times like merge windows. To be fair, this isn't a ping or a resend. It's addressing comments that were given in v8 that was sent out on Tuesday. This isn't v1, where I would agree with waiting a week for comments. v1 was sent back in 3/6. I do not expect (nor want) someone to wait a week on v8 for all feedback to come in, unless it was a redesign of the code. But it's now starting to settle, and that "week waiting" period isn't necessary for fixing up minor suggestions by the reviewers. I was hoping this would be good to go by the end of the week, so I could get it into linux-next by next week. -- Steve