From: Kees Cook <keescook@chromium.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Thorsten Leemhuis <linux@leemhuis.info>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stefano Zacchiroli <zack@upsilon.cc>,
Steven Rostedt <rostedt@goodmis.org>,
Laura Abbott <labbott@kernel.org>,
Julia Lawall <julia.lawall@inria.fr>,
Wenwen Wang <wenwen@cs.uga.edu>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] Documentation/process: Add Researcher Guidelines
Date: Fri, 4 Mar 2022 10:15:52 -0800 [thread overview]
Message-ID: <202203041014.12E6F25@keescook> (raw)
In-Reply-To: <871qzhhc39.fsf@meer.lwn.net>
On Fri, Mar 04, 2022 at 10:16:58AM -0700, Jonathan Corbet wrote:
> Sorry, been a bit distracted...when we were working on this I was more
> focused on the text than the location. My own feeling is that
> Documentation/process is a better place for this - that's where we tell
> the world how to work with the kernel community, after all. I'm not
> going to dig in my heels and fight about it, but that's my sense.
I had no strong preference. I've moved it to /process now.
> Otherwise, it kind of seems like this is ready to go in. I'd like to
> apply it before the merge window; lemme know where you want it in the
> end and we can get it done.
Agreed. v2 had v1's feedback addressed, and v2 was not further commented
on. v3 now here:
https://lore.kernel.org/lkml/20220304181418.1692016-1-keescook@chromium.org
--
Kees Cook
prev parent reply other threads:[~2022-03-04 18:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 0:14 [PATCH] Documentation/process: Add Researcher Guidelines Kees Cook
2022-02-24 1:00 ` Gustavo A. R. Silva
2022-02-25 19:14 ` Kees Cook
2022-02-24 8:19 ` Thorsten Leemhuis
2022-02-24 9:56 ` Alexander Dahl
2022-02-24 10:10 ` Thorsten Leemhuis
2022-02-25 18:55 ` Kees Cook
2022-03-04 17:16 ` Jonathan Corbet
2022-03-04 17:20 ` Randy Dunlap
2022-03-04 18:15 ` Kees Cook [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=202203041014.12E6F25@keescook \
--to=keescook@chromium.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--cc=labbott@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=rostedt@goodmis.org \
--cc=wenwen@cs.uga.edu \
--cc=zack@upsilon.cc \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.