[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPDLWs_aUbt3Vdg1avkoSq_Gpr19TQ2hhrhA1G6-THAXUP07jQ@mail.gmail.com>
Date: Thu, 12 Jan 2017 15:34:08 +0530
From: Kaiwan N Billimoria <kaiwan@...wantech.com>
To: kernel-hardening@...ts.openwall.com
Cc: Kees Cook <keescook@...omium.org>
Subject: Re: New to KSPP, would like to contribute
Thanks Greg.
Will do..
Regards,
Kaiwan.
Kaiwan N Billimoria
✉ kaiwan@...wantech.com
✉ kaiwan.billimoria@...il.com
kaiwanTECH
http://kaiwantech.in
Do visit our enhanced website.
4931, 11th Floor, Highpoint IV, 45 Palace Road, Bangalore 560 001.
☎ +91.9845016788 (M)
☎ TeleFax: +91.80.22389396 | Alt. Tel: +91.80.64500257
LinkedIn: https://in.linkedin.com/in/kaiwanbillimoria
I blog here:
Tech : http://kaiwantech.wordpress.com |
Running : http://kaiwanbill.blogspot.in/
"Don't be afraid that your life will end,
be afraid that it will never begin."
On Thu, Jan 12, 2017 at 1:07 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
> 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
>
>
Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
