RE: [PATCH v3 2/2] edac: zynqmp_ocm: Add EDAC support for ZynqMP OCM

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

 



> -----Original Message-----
> From: Sai Krishna Potthuri <sai.krishna.potthuri@xxxxxxx>
> Sent: Friday, August 26, 2022 2:54 AM
> Subject: [PATCH v3 2/2] edac: zynqmp_ocm: Add EDAC support for ZynqMP OCM
> 
...
>  create mode 100644 drivers/edac/zynqmp_ocm_edac.c
> 
> +		snprintf(priv->message, ZYNQMP_OCM_EDAC_MSG_SIZE,
> +			 "\n\rOCM ECC error type :%s\n\r"
> +			 "Addr: [0x%X]\n\rFault Data[31:0]: [0x%X]\n\r"
> +			 "Fault Data[63:32]: [0x%X]",
> +			 "CE", pinf->addr, pinf->data0, pinf->data1);

What are all these strange line endings?

Historically, Microsoft Windows used \r\n, UNIX and Linux 
used \n, and Macs used \r, but \n\r seems completely wrong.





[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]


  Powered by Linux