On 11 January 2018 at 08:36, Konstantin Ryabitsev
wrote:
> Let me do this -- I'll go ahead and produce the document I think would be
> good for kernel devs, based on the more generic document I mentioned
> earlier. Then I will get in touch again so we can see if that version is
> something that sh
On Thu, 18 Jan 2018, Randy Dunlap wrote:
> On 01/18/2018 06:09 AM, Jani Nikula wrote:
>> On Thu, 11 Jan 2018, Konstantin Ryabitsev
>> wrote:
>>> On Wed, Jan 10, 2018 at 02:05:16PM -0700, Jonathan Corbet wrote:
> Does such document belong with the rest of the kernel docs in the
> tree,
>
On 01/18/2018 06:09 AM, Jani Nikula wrote:
> On Thu, 11 Jan 2018, Konstantin Ryabitsev
> wrote:
>> On Wed, Jan 10, 2018 at 02:05:16PM -0700, Jonathan Corbet wrote:
Does such document belong with the rest of the kernel docs in the
tree,
or should it remain fully external? I'll be h
On Thu, 11 Jan 2018, Konstantin Ryabitsev
wrote:
> On Wed, Jan 10, 2018 at 02:05:16PM -0700, Jonathan Corbet wrote:
>>> Does such document belong with the rest of the kernel docs in the
>>> tree,
>>> or should it remain fully external? I'll be happy to port it to RST if
>>> you think it should l
On Wed, Jan 10, 2018 at 02:05:16PM -0700, Jonathan Corbet wrote:
Does such document belong with the rest of the kernel docs in the
tree,
or should it remain fully external? I'll be happy to port it to RST if
you think it should live alongside other documents like coding
standards.
My immediate
On Tue, 9 Jan 2018 16:40:48 -0500
Konstantin Ryabitsev wrote:
> Does such document belong with the rest of the kernel docs in the tree,
> or should it remain fully external? I'll be happy to port it to RST if
> you think it should live alongside other documents like coding
> standards.
My imm
Hi, all:
I would like to adapt this document to be more specific to kernel
development:
https://github.com/lfit/itpol/blob/master/protecting-code-integrity.md
This stems from many back-and-forth conversations with kernel devs, and
I believe many would benefit from such guide, especially sin
