From: Greg KH <gregkh@linuxfoundation.org>
To: "Günther Noack" <gnoack@google.com>
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>
Subject: Re: [PATCH] Restrict access to TIOCLINUX
Date: Wed, 23 Aug 2023 16:36:54 +0200 [thread overview]
Message-ID: <2023082320-jogging-kissing-a700@gregkh> (raw)
In-Reply-To: <ZOT8zL8tXqy41XmM@google.com>
On Tue, Aug 22, 2023 at 08:22:04PM +0200, Günther Noack wrote:
> By the non-submittable "form", I assume you mean the formatting and maybe
> phrasing of the e-mail, so that it can be cleanly applied to git? Or was there
> anything in the code which I missed?
I only looked at the format, that was incorrect. You can test the patch
to verify if the code is correct before submitting it :)
thanks,
greg k-h
prev parent reply other threads:[~2023-08-23 14:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 14:08 [PATCH] Restrict access to TIOCLINUX Hanno Böck
2023-04-02 14:55 ` Greg KH
2023-04-02 17:16 ` Hanno Böck
2023-04-02 17:23 ` Greg KH
2023-04-02 17:33 ` Hanno Böck
2023-04-02 17:44 ` Greg KH
2023-04-04 21:54 ` Jordan Glover
2023-08-18 16:10 ` Günther Noack
2023-08-22 12:07 ` Greg KH
2023-08-22 12:51 ` Boris Lukashev
2023-08-22 13:34 ` Greg KH
2023-08-22 18:22 ` Günther Noack
2023-08-23 14:36 ` Greg KH [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=2023082320-jogging-kissing-a700@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Dave@mielke.cc \
--cc=David.Laight@aculab.com \
--cc=geert@linux-m68k.org \
--cc=gnoack@google.com \
--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=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).