From ae8b815355a19236acab80846bcb23c5f67347bb Mon Sep 17 00:00:00 2001
From: "Kenneth Benzie (Benie)" <k.benzie@codeplay.com>
Date: Tue, 20 Jun 2023 15:00:25 +0100
Subject: [PATCH] [ur] Cleanup inconsistent file properties

* Remove the executable bit from source files
* Run `dos2unix` on all source files
---
 scripts/core/EXP-USM-IMPORT-RELEASE.rst | 116 ++++++++++++------------
 scripts/core/INTRO.rst                  |   2 +-
 scripts/core/PROG.rst                   |   2 +-
 scripts/core/exp-usm-import-release.yml |   0
 4 files changed, 60 insertions(+), 60 deletions(-)
 mode change 100755 => 100644 scripts/core/EXP-USM-IMPORT-RELEASE.rst
 mode change 100755 => 100644 scripts/core/exp-usm-import-release.yml

diff --git a/scripts/core/EXP-USM-IMPORT-RELEASE.rst b/scripts/core/EXP-USM-IMPORT-RELEASE.rst
old mode 100755
new mode 100644
index 055991755b..03a1e464a2
--- a/scripts/core/EXP-USM-IMPORT-RELEASE.rst
+++ b/scripts/core/EXP-USM-IMPORT-RELEASE.rst
@@ -1,58 +1,58 @@
-
-<%
-    OneApi=tags['$OneApi']
-    x=tags['$x']
-    X=x.upper()
-%>
-.. _experimental-usm-import-release:
-
-==================
-USM Import/Release
-==================
-
-.. warning::
-
-    Experimental features:
-
-    *   May be replaced, updated, or removed at any time.
-    *   Do not require maintaining API/ABI stability of their own additions over
-        time.
-    *   Do not require conformance testing of their own additions.
-
-
-Data transfer between Host and Device is most efficient when source and
-destination are both allocated in USM memory.
-In situations where host data will participate in host/device transfers
-and the host data allocation is under user control, USM functions
-such as malloc_host could be used to allocate USM memory instead of
-system memory.
-However, this is not always possible if the source code where the allocation
-is made is not available, or source code changes are prohibited for portability
-reasons.
-In these situations a mechanism to temporarily promote system memory to USM
-for the duration of the host/device data transfers is useful for maximizing
-data transfer rate.
-
-
-Import Host Memory into USM
-===========================
-
-Import a range of host memory into USM.
-
-.. parsed-literal::
-
-    // Import into USM
-    ${x}USMImportExp(hContext, hostPtr, size);
-            
-Release Host Memory Previously Imported into USM
-================================================
-
-Release from USM a range of memory that had been previously imported
-into USM.
-
-
-.. parsed-literal::
-
-    // Release from USM
-    ${x}USMReleaseExp(hContext, hostPtr);
-
+
+<%
+    OneApi=tags['$OneApi']
+    x=tags['$x']
+    X=x.upper()
+%>
+.. _experimental-usm-import-release:
+
+==================
+USM Import/Release
+==================
+
+.. warning::
+
+    Experimental features:
+
+    *   May be replaced, updated, or removed at any time.
+    *   Do not require maintaining API/ABI stability of their own additions over
+        time.
+    *   Do not require conformance testing of their own additions.
+
+
+Data transfer between Host and Device is most efficient when source and
+destination are both allocated in USM memory.
+In situations where host data will participate in host/device transfers
+and the host data allocation is under user control, USM functions
+such as malloc_host could be used to allocate USM memory instead of
+system memory.
+However, this is not always possible if the source code where the allocation
+is made is not available, or source code changes are prohibited for portability
+reasons.
+In these situations a mechanism to temporarily promote system memory to USM
+for the duration of the host/device data transfers is useful for maximizing
+data transfer rate.
+
+
+Import Host Memory into USM
+===========================
+
+Import a range of host memory into USM.
+
+.. parsed-literal::
+
+    // Import into USM
+    ${x}USMImportExp(hContext, hostPtr, size);
+
+Release Host Memory Previously Imported into USM
+================================================
+
+Release from USM a range of memory that had been previously imported
+into USM.
+
+
+.. parsed-literal::
+
+    // Release from USM
+    ${x}USMReleaseExp(hContext, hostPtr);
+
diff --git a/scripts/core/INTRO.rst b/scripts/core/INTRO.rst
index 9b92b891bb..27ec1eca59 100644
--- a/scripts/core/INTRO.rst
+++ b/scripts/core/INTRO.rst
@@ -1,4 +1,4 @@
-
+
 <%
     OneApi=tags['$OneApi']
     x=tags['$x']
diff --git a/scripts/core/PROG.rst b/scripts/core/PROG.rst
index 89784236ef..280144adcd 100644
--- a/scripts/core/PROG.rst
+++ b/scripts/core/PROG.rst
@@ -1,4 +1,4 @@
-
+
 <%
     OneApi=tags['$OneApi']
     x=tags['$x']
diff --git a/scripts/core/exp-usm-import-release.yml b/scripts/core/exp-usm-import-release.yml
old mode 100755
new mode 100644