From: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
To: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: mahesh@linux.vnet.ibm.com, tachibana@mxm.nes.nec.co.jp,
kexec@lists.infradead.org, ananth@in.ibm.com,
buendgen@de.ibm.com
Subject: Re: [PATCH 0/7] makedumpfile security key filtering with eppic
Date: Mon, 15 Oct 2012 12:34:12 +0530 [thread overview]
Message-ID: <507BB56C.5080304@linux.vnet.ibm.com> (raw)
In-Reply-To: <20121015134650.9be8ae8a4a0af9869c7aedf5@mxc.nes.nec.co.jp>
Hi Atsushi,
On 2012-10-15 10:16, Atsushi Kumagai wrote:
> Hello Mahesh,
>
> On Fri, 12 Oct 2012 10:59:17 +0530
> Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com> wrote:
>
>> On 08/17/2012 09:46 AM, Atsushi Kumagai wrote:
>>> Hello Aravinda,
>>>
>>> On Thu, 16 Aug 2012 11:55:55 +0530
>>> Aravinda Prasad <aravinda@linux.vnet.ibm.com> wrote:
>>>
>>>> Hello Kumagai-san,
>>>>
>>>> Did you get a chance to review the makedumpfile security key enhancement
>>>> patches?
>>>>
>>>> - Aravinda
>>>
>>> Sorry for not responding.
>>>
>>> I'm afraid that I can't start to review them yet.
>>> I've been working on the cyclic mode feature for a few months,
>>> and I'm now preparing the next release including the feature.
>>>
>>> I'll release the next version soon, I'll review your patches after that.
>>>
>>
>> Hi Atsushi,
>>
>> Did you get chance to review these patches?
>
> I'm sorry for keeping you waiting.
> I have just started reviewing these patches, I have a comment for them.
>
> These patches require all users to prepare libeppic, but I think
> it's not good implementation because everyone has to build libeppic
> from the source code themselves, it isn't desirable for the users who
> don't need to use this feature.
>
> So, I hope to change them to optional like LZO and snappy compression.
> Is it possible ?
Yes it is possible.
I will update the patch to have eppic as optional like LZO. I will
include this along with other changes based on your review comments.
>
>
> Thanks
> Atsushi Kumagai
>
--
Regards,
Aravinda
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-10-15 7:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 10:04 [PATCH 0/7] makedumpfile security key filtering with eppic Aravinda Prasad
2012-06-06 10:04 ` [PATCH 1/7] Initialize and setup eppic Aravinda Prasad
2012-06-06 10:05 ` [PATCH 2/7] makedumpfile and eppic interface layer Aravinda Prasad
2012-06-06 10:05 ` [PATCH 3/7] Eppic call back functions to query a dump image Aravinda Prasad
2012-06-06 10:06 ` [PATCH 4/7] Implement apigetctype call back function Aravinda Prasad
2012-10-29 8:06 ` Atsushi Kumagai
2012-06-06 10:06 ` [PATCH 5/7] Implement apimember and apigetrtype call back functions Aravinda Prasad
2012-06-06 10:06 ` [PATCH 6/7] Extend eppic built-in functions to include memset function Aravinda Prasad
2012-06-06 10:07 ` [PATCH 7/7] Support fully typed symbol access mode Aravinda Prasad
2012-06-11 8:44 ` [PATCH 0/7] makedumpfile security key filtering with eppic Atsushi Kumagai
2012-08-16 6:25 ` Aravinda Prasad
2012-08-17 4:16 ` Atsushi Kumagai
2012-10-12 5:29 ` Mahesh Jagannath Salgaonkar
2012-10-15 4:46 ` Atsushi Kumagai
2012-10-15 7:04 ` Aravinda Prasad [this message]
2012-10-29 8:06 ` Atsushi Kumagai
2012-10-29 10:15 ` Aravinda Prasad
2012-10-31 4:21 ` Atsushi Kumagai
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=507BB56C.5080304@linux.vnet.ibm.com \
--to=aravinda@linux.vnet.ibm.com \
--cc=ananth@in.ibm.com \
--cc=buendgen@de.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=mahesh@linux.vnet.ibm.com \
--cc=tachibana@mxm.nes.nec.co.jp \
/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.