From: Kees Cook <keescook@chromium.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Günther Noack" <gnoack@google.com>,
"Samuel Thibault" <samuel.thibault@ens-lyon.org>,
"Hanno Böck" <hanno@hboeck.de>,
kernel-hardening@lists.openwall.com,
"Jiri Slaby" <jirislaby@kernel.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Paul Moore" <paul@paul-moore.com>,
"David Laight" <David.Laight@aculab.com>,
"Simon Brand" <simon.brand@postadigitale.de>,
"Dave Mielke" <Dave@mielke.cc>,
"Mickaël Salaün" <mic@digikod.net>,
"KP Singh" <kpsingh@google.com>,
"Nico Schottelius" <nico-gpm2008@schottelius.org>
Subject: sending commit notification to patch thread (was "Re: [PATCH v3 0/1] Restrict access to TIOCLINUX")
Date: Wed, 11 Oct 2023 08:49:51 -0700 [thread overview]
Message-ID: <202310110847.1BDD74DB@keescook> (raw)
In-Reply-To: <2023101158-esteemed-condiment-1dd6@gregkh>
On Wed, Oct 11, 2023 at 08:22:49AM +0200, Greg KH wrote:
> What b4 option does a "I applied this patch" response? The
> --cc-trailers option to 'shazam'? Or something else?
If you're using "b4 shazam", then it'll keep a record of it already and
you can use "b4 ty" to send the "thank you" email to the thread.
--
Kees Cook
prev parent reply other threads:[~2023-10-11 15:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 16:41 [PATCH v3 0/1] Restrict access to TIOCLINUX Günther Noack
2023-08-28 16:41 ` [PATCH v3 1/1] tty: Restrict access to TIOCLINUX' copy-and-paste subcommands Günther Noack
2023-08-28 18:43 ` Mickaël Salaün
2023-08-28 18:48 ` Greg KH
2023-08-28 16:45 ` [PATCH v3 0/1] Restrict access to TIOCLINUX Samuel Thibault
2023-08-29 13:00 ` Günther Noack
2023-08-30 0:36 ` Samuel Thibault
2023-09-15 13:32 ` Günther Noack
2023-10-09 20:19 ` Kees Cook
2023-10-10 6:17 ` Greg KH
2023-10-10 22:23 ` Kees Cook
2023-10-11 6:22 ` Greg KH
2023-10-11 15:49 ` 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=202310110847.1BDD74DB@keescook \
--to=keescook@chromium.org \
--cc=Dave@mielke.cc \
--cc=David.Laight@aculab.com \
--cc=geert@linux-m68k.org \
--cc=gnoack@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hanno@hboeck.de \
--cc=jirislaby@kernel.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=kpsingh@google.com \
--cc=mic@digikod.net \
--cc=nico-gpm2008@schottelius.org \
--cc=paul@paul-moore.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=simon.brand@postadigitale.de \
/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;
as well as URLs for NNTP newsgroup(s).