Re: [PATCH 3/7 v4] CPER: Adjust code flow of some functions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, May 21, 2014 at 01:05:21PM +0200, Borislav Petkov wrote:
> > +const char *cper_mem_err_type_str(unsigned int etype)
> >  {
> > -	if (mem->validation_bits & CPER_MEM_VALID_ERROR_STATUS)
> > -		printk("%s""error_status: 0x%016llx\n", pfx, mem->error_status);
> > -	if (mem->validation_bits & CPER_MEM_VALID_PA)
> > -		printk("%s""physical_address: 0x%016llx\n",
> > -		       pfx, mem->physical_addr);
> > -	if (mem->validation_bits & CPER_MEM_VALID_PA_MASK)
> > -		printk("%s""physical_address_mask: 0x%016llx\n",
> 
> The physical address mask is still not part of the tracepoint as a u8 as
> we talked.
> 
I thought out discussion is only for trace part. But it is OK to me to
make whole style aligned.

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux