linux-kernel - Re: [PATCH v9 0/8] function_graph: Support recording and printing the return value of function

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20230330101526.2c862a42@gandalf.local.home>
Date:   Thu, 30 Mar 2023 10:15:26 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Donglin Peng <pengdonglin@...gfor.com.cn>, mhiramat@...nel.org,
        linux@...linux.org.uk, mark.rutland@....com, will@...nel.org,
        catalin.marinas@....com, rmk+kernel@...linux.org.uk,
        palmer@...belt.com, paul.walmsley@...ive.com,
        aou@...s.berkeley.edu, tglx@...utronix.de,
        dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
        chenhuacai@...nel.org, zhangqing@...ngson.cn, kernel@...0n.name,
        mingo@...hat.com, peterz@...radead.org, xiehuan09@...il.com,
        dinghui@...gfor.com.cn, huangcun@...gfor.com.cn,
        dolinux.peng@...il.com, linux-trace-kernel@...r.kernel.org,
        loongarch@...ts.linux.dev, linux-riscv@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v9 0/8] function_graph: Support recording and printing
 the return value of function

On Thu, 30 Mar 2023 15:59:48 +0200
Borislav Petkov <bp@...en8.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