From: "Günther Noack" <gnoack@google.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Hanno Böck" <hanno@hboeck.de>,
kernel-hardening@lists.openwall.com,
"Kees Cook" <keescook@chromium.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Paul Moore" <paul@paul-moore.com>,
"Samuel Thibault" <samuel.thibault@ens-lyon.org>,
"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: Re: [PATCH v2 1/1] tty: Restrict access to TIOCLINUX' copy-and-paste subcommands
Date: Mon, 28 Aug 2023 18:42:58 +0200 [thread overview]
Message-ID: <ZOzOkt8/Icws1+Vn@google.com> (raw)
In-Reply-To: <2023082836-masses-gyration-0e7e@gregkh>
On Mon, Aug 28, 2023 at 04:48:28PM +0200, Greg KH wrote:
> On Mon, Aug 28, 2023 at 02:21:09PM +0200, Günther Noack wrote:
> > Signed-off-by: Hanno Böck <hanno@hboeck.de>
> > Tested-by: Günther Noack <gnoack@google.com>
>
> When you pass on a patch like this, you too need to sign off on it as
> per the instructions in the DCO. I'm pretty sure the Google open source
> training also says that, but maybe not. If not, it should :)
Ah sorry -- fixed and re-sent.
—Günther
--
Sent using Mutt 🐕 Woof Woof
prev parent reply other threads:[~2023-08-28 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 12:21 [PATCH v2 0/1] Restrict access to TIOCLINUX Günther Noack
2023-08-28 12:21 ` [PATCH v2 1/1] tty: Restrict access to TIOCLINUX' copy-and-paste subcommands Günther Noack
2023-08-28 14:48 ` Greg KH
2023-08-28 16:42 ` Günther Noack [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=ZOzOkt8/Icws1+Vn@google.com \
--to=gnoack@google.com \
--cc=Dave@mielke.cc \
--cc=David.Laight@aculab.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=hanno@hboeck.de \
--cc=jirislaby@kernel.org \
--cc=keescook@chromium.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 read-only IMAP folder(s) and NNTP newsgroup(s).