From: Steven Rostedt <rostedt@goodmis.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Donglin Peng <pengdonglin@sangfor.com.cn>,
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
Date: Thu, 30 Mar 2023 10:15:26 -0400 [thread overview]
Message-ID: <20230330101526.2c862a42@gandalf.local.home> (raw)
In-Reply-To: <20230330135948.GCZCWV1O/IjsxsBmN8@fat_crate.local>
On Thu, 30 Mar 2023 15:59:48 +0200
Borislav Petkov <bp@alien8.de> 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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-03-30 14:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 11:39 [PATCH v9 0/8] function_graph: Support recording and printing the return value of function Donglin Peng
2023-03-30 11:39 ` [PATCH v9 1/8] " Donglin Peng
2023-03-30 11:39 ` [PATCH v9 2/8] tracing: Add documentation for funcgraph-retval and funcgraph-retval-hex Donglin Peng
2023-03-30 11:39 ` [PATCH v9 3/8] ARM: ftrace: Enable HAVE_FUNCTION_GRAPH_RETVAL Donglin Peng
2023-03-30 11:39 ` [PATCH v9 4/8] arm64: " Donglin Peng
2023-03-30 11:39 ` [PATCH v9 5/8] riscv: " Donglin Peng
2023-03-30 11:39 ` [PATCH v9 6/8] x86/ftrace: " Donglin Peng
2023-03-30 11:39 ` [PATCH v9 7/8] LoongArch: ftrace: " Donglin Peng
2023-03-30 12:48 ` Huacai Chen
2023-03-30 13:07 ` Donglin Peng
2023-03-30 11:39 ` [PATCH v9 8/8] selftests/ftrace: Add funcgraph-retval test case Donglin Peng
2023-03-30 13:59 ` [PATCH v9 0/8] function_graph: Support recording and printing the return value of function Borislav Petkov
2023-03-30 14:15 ` Steven Rostedt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230330101526.2c862a42@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=aou@eecs.berkeley.edu \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=dinghui@sangfor.com.cn \
--cc=dolinux.peng@gmail.com \
--cc=hpa@zytor.com \
--cc=huangcun@sangfor.com.cn \
--cc=kernel@xen0n.name \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=loongarch@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pengdonglin@sangfor.com.cn \
--cc=peterz@infradead.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=xiehuan09@gmail.com \
--cc=zhangqing@loongson.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox