All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: kernel-hardening@lists.openwall.com
Cc: Kees Cook <keescook@chromium.org>
Subject: Re: [kernel-hardening] New to KSPP, would like to contribute
Date: Thu, 12 Jan 2017 08:37:46 +0100	[thread overview]
Message-ID: <20170112073746.GA23596@kroah.com> (raw)
In-Reply-To: <CAPDLWs8dMyk3CGpt49w0Nyd59ZDDOSMz87vkm5k7NkObAZNzog@mail.gmail.com>

On Thu, Jan 12, 2017 at 09:01:05AM +0530, Kaiwan N Billimoria wrote:
> Okay, thanks, I see it better now :)
> 
> Forgive my silly qs: 
> so as I understand it, the objective is to start merging in some of the grsec
> code into mainline, yes? So, which kernel do we work on? the latest rc or do I
> work on the one where the above patch applies (i.e. 4.8.17)?

You can't go back in time and get stuff merged into an old patch, so
always work on the latest kernel tree.  Use linux-next so you don't end
up duplicating any effort that people have already done.

I suggest reading Documentation/development_process/ as a summary of how
all of this works.

thanks,

greg k-h

  reply	other threads:[~2017-01-12  7:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-07  7:43 [kernel-hardening] New to KSPP, would like to contribute Kaiwan N Billimoria
2017-01-10  0:27 ` Kees Cook
2017-01-10 12:42   ` Kaiwan N Billimoria
2017-01-10 20:25     ` Kees Cook
2017-01-12  3:31       ` Kaiwan N Billimoria
2017-01-12  7:37         ` Greg KH [this message]
2017-01-12 10:04           ` Kaiwan N Billimoria
2017-01-17  7:38             ` Kaiwan N Billimoria
2017-01-17  7:44               ` Kaiwan N Billimoria
2017-01-17  7:52               ` Greg KH

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=20170112073746.GA23596@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.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.