On 10/25/2017 03:51 AM, Jarkko Sakkinen wrote:
I noticed when making slides for KS that the naming for event log stuff
that the naming is so broken that it is hard to understand the code.
Here it really would make sense to have a patch set just to clean up the
cruft.
Random examples of more se
On Thu, Oct 26, 2017 at 4:14 PM, Jarkko Sakkinen
wrote:
> On Wed, Oct 25, 2017 at 03:18:48PM +0200, Jarkko Sakkinen wrote:
>> > Since this may conflict with the last patch set I sent, are you happy
>> > for me to base this new set on tpmdd/master?
>>
>> What about this: you do an updated version o
On Wed, Oct 25, 2017 at 03:18:48PM +0200, Jarkko Sakkinen wrote:
> > Since this may conflict with the last patch set I sent, are you happy
> > for me to base this new set on tpmdd/master?
>
> What about this: you do an updated version of your patch set that
> includes these clean ups?
>
> PS. Sor
On Wed, Oct 25, 2017 at 10:43:10AM +0200, Thiebaud Weksteen wrote:
> On Wed, Oct 25, 2017 at 12:21 AM, Jarkko Sakkinen
> wrote:
> > I noticed when making slides for KS that the naming for event log stuff
> > that the naming is so broken that it is hard to understand the code.
> > Here it really wo
On Wed, Oct 25, 2017 at 12:21 AM, Jarkko Sakkinen
wrote:
> I noticed when making slides for KS that the naming for event log stuff
> that the naming is so broken that it is hard to understand the code.
> Here it really would make sense to have a patch set just to clean up the
> cruft.
Agreed and
I noticed when making slides for KS that the naming for event log stuff
that the naming is so broken that it is hard to understand the code.
Here it really would make sense to have a patch set just to clean up the
cruft.
Random examples of more senseful naming:
* tpm2_bios_measurements_start() sh
6 matches
Mail list logo