From: Greg KH <gregkh@linuxfoundation.org>
To: Rick Mark <rickmark@outlook.com>
Cc: "kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
"keescook@chromium.org" <keescook@chromium.org>
Subject: Re: Hello Kernel Hardening
Date: Thu, 1 Aug 2019 22:25:38 +0200 [thread overview]
Message-ID: <20190801202538.GA4383@kroah.com> (raw)
In-Reply-To: <BYAPR07MB57828912977C33ABC45E4E10DADE0@BYAPR07MB5782.namprd07.prod.outlook.com>
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, Aug 01, 2019 at 08:00:33PM +0000, Rick Mark wrote:
> Awesome,
>
> Thanks Greg for the advice and welcome.
A bit more advice above on how the kernel developers handle email :)
> I'm already starting to put together one with Linaro / OP-TEE cross
> compiled for QEMU ARMv8. I'll send it back out when it's working /
> not shameful enough to actually `git push` to a fork.
I would recommend reading the kernel development process documentation
as well, in the kernel source tree. That will give you a good idea as
to how we work and how we handle reviewing patches (hint, we don't use
git trees for review).
good luck!
greg k-h
prev parent reply other threads:[~2019-08-01 20:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 6:52 Hello Kernel Hardening Rick Mark
2019-07-31 9:18 ` Greg KH
2019-07-31 19:55 ` Kees Cook
2019-07-31 20:33 ` Rick Mark
2019-08-01 5:54 ` Greg KH
2019-08-01 20:00 ` Rick Mark
2019-08-01 20:25 ` 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=20190801202538.GA4383@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=rickmark@outlook.com \
/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.