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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <MW5PR84MB18420EE64EA9B9FCD2E3ABAAAB759@MW5PR84MB1842.NAMPRD84.PROD.OUTLOOK.COM>
Date:   Fri, 26 Aug 2022 23:32:34 +0000
From:   "Elliott, Robert (Servers)" <elliott@....com>
To:     Sai Krishna Potthuri <sai.krishna.potthuri@....com>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Michal Simek <michal.simek@...inx.com>,
        Borislav Petkov <bp@...en8.de>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Tony Luck <tony.luck@...el.com>,
        James Morse <james.morse@....com>,
        "Robert Richter" <rric@...nel.org>
CC:     "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
        "saikrishna12468@...il.com" <saikrishna12468@...il.com>,
        "git@....com" <git@....com>,
        Shubhrajyoti Datta <shubhrajyoti.datta@....com>
Subject: RE: [PATCH v3 2/2] edac: zynqmp_ocm: Add EDAC support for ZynqMP OCM

> -----Original Message-----
> From: Sai Krishna Potthuri <sai.krishna.potthuri@....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.