lkml.org 
[lkml]   [2022]   [Aug]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [PATCH v3 2/2] edac: zynqmp_ocm: Add EDAC support for ZynqMP OCM
Date
> -----Original Message-----
> From: Sai Krishna Potthuri <sai.krishna.potthuri@amd.com>
> 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.

\
 
 \ /
  Last update: 2022-08-27 01:35    [W:0.100 / U:0.572 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site