linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nayna <nayna@linux.vnet.ibm.com>
To: prsriva <prsriva@linux.microsoft.com>,
	Prakhar Srivastava <prsriva02@gmail.com>,
	linux-integrity@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	inux-security-module@vger.kernel.org, zohar@linux.ibm.com,
	ebiederm@xmission.com, vgoyal@redhat.com,
	Prakhar Srivastava <prsriva@microsoft.com>
Subject: Re: [PATCH v2 2/5 RFC] use event name instead of enum to make the call generic
Date: Thu, 25 Apr 2019 14:41:53 -0400	[thread overview]
Message-ID: <ccdcd117-9b34-ba01-b087-561642447af4@linux.vnet.ibm.com> (raw)
In-Reply-To: <4c313367-22dc-9532-54b5-cd3a79deb625@linux.microsoft.com>



On 04/25/2019 01:19 PM, prsriva wrote:
> On 2019-04-25 4:48 a.m., Nayna wrote:
>>
>>
>> On 04/23/2019 08:15 PM, Prakhar Srivastava wrote:
>>> From: Prakhar Srivastava <prsriva02@gmail.com>
>>>
>>> Signed-off-by: Prakhar Srivastava <prsriva@microsoft.com>
>>> ---
>>>
>> The v2 version has to be on top of the HEAD of the repository itself, 
>> and not on the v1 version. Only the final reviewed and tested version 
>> makes to the upstream.
>>
>> Btw, which repository and its branch are you using ?
>>
> I am basing my changes off IMA branch:
> git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git

Ok. Please use either next-integrity branch or James Morris next-general 
or next-testing.

Thanks & Regards,
       - Nayna



  parent reply	other threads:[~2019-04-25 18:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24  0:15 [PATCH v2 1/5 RFC] added ima hook for buffer, being enabled as a policy Prakhar Srivastava
2019-04-24  0:15 ` [PATCH v2 2/5 RFC] use event name instead of enum to make the call generic Prakhar Srivastava
2019-04-25 11:48   ` Nayna
2019-04-25 17:19     ` prsriva
2019-04-25 18:31       ` Linus Torvalds
2019-04-25 22:34         ` James Morris
2019-04-25 23:18           ` James Bottomley
2019-04-26  0:03             ` James Morris
2019-04-25 23:19           ` Linus Torvalds
2019-04-25 18:41       ` Nayna [this message]
2019-04-24  0:15 ` [PATCH v2 3/5 RFC] since cmdline args can be same for multiple kexec, log entry hash will collide. Prepend the kernel file name to the cmdline args to distinguish between cmdline args passed to subsequent kexec calls Prakhar Srivastava
2019-04-24  0:15 ` [PATCH v2 4/5 RFC] added a buffer_check LSM hook Prakhar Srivastava
2019-04-24  0:15 ` [PATCH v2 5/5 RFC] add the buffer to the event data in ima free entry data if store_template failed added check in templates for buffer Prakhar Srivastava

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=ccdcd117-9b34-ba01-b087-561642447af4@linux.vnet.ibm.com \
    --to=nayna@linux.vnet.ibm.com \
    --cc=ebiederm@xmission.com \
    --cc=inux-security-module@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prsriva02@gmail.com \
    --cc=prsriva@linux.microsoft.com \
    --cc=prsriva@microsoft.com \
    --cc=vgoyal@redhat.com \
    --cc=zohar@linux.ibm.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 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 NNTP newsgroup(s).