* [PATCH] firmware: ti_sci: Use the correct style for SPDX License Identifier
@ 2019-06-14 13:57 Nishad Kamdar
2019-06-14 14:53 ` Lokesh Vutla
2019-06-19 4:35 ` santosh.shilimkar
0 siblings, 2 replies; 3+ messages in thread
From: Nishad Kamdar @ 2019-06-14 13:57 UTC (permalink / raw)
To: Nishanth Menon, Tero Kristo, Santosh Shilimkar
Cc: Greg Kroah-Hartman, Joe Perches, Uwe Kleine-König,
linux-arm-kernel, linux-kernel
This patch corrects the SPDX License Identifier style
in header file related to Firmware Drivers for Texas
Instruments SCI Protocol.
For C header files Documentation/process/license-rules.rst
mandates C-like comments (opposed to C source files where
C++ style should be used)
Changes made by using a script provided by Joe Perches here:
https://lkml.org/lkml/2019/2/7/46
Suggested-by: Joe Perches <joe@perches.com>
Signed-off-by: Nishad Kamdar <nishadkamdar@gmail.com>
---
drivers/firmware/ti_sci.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/firmware/ti_sci.h b/drivers/firmware/ti_sci.h
index 662dcffef311..d7b4cd3fce8f 100644
--- a/drivers/firmware/ti_sci.h
+++ b/drivers/firmware/ti_sci.h
@@ -1,4 +1,4 @@
-// SPDX-License-Identifier: BSD-3-Clause
+/* SPDX-License-Identifier: BSD-3-Clause */
/*
* Texas Instruments System Control Interface (TISCI) Protocol
*
--
2.17.1
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] firmware: ti_sci: Use the correct style for SPDX License Identifier
2019-06-14 13:57 [PATCH] firmware: ti_sci: Use the correct style for SPDX License Identifier Nishad Kamdar
@ 2019-06-14 14:53 ` Lokesh Vutla
2019-06-19 4:35 ` santosh.shilimkar
1 sibling, 0 replies; 3+ messages in thread
From: Lokesh Vutla @ 2019-06-14 14:53 UTC (permalink / raw)
To: Nishad Kamdar, Nishanth Menon, Tero Kristo, Santosh Shilimkar
Cc: Joe Perches, Greg Kroah-Hartman, linux-kernel, linux-arm-kernel,
Uwe Kleine-König
On 14/06/19 7:27 PM, Nishad Kamdar wrote:
> This patch corrects the SPDX License Identifier style
> in header file related to Firmware Drivers for Texas
> Instruments SCI Protocol.
> For C header files Documentation/process/license-rules.rst
> mandates C-like comments (opposed to C source files where
> C++ style should be used)
>
> Changes made by using a script provided by Joe Perches here:
> https://lkml.org/lkml/2019/2/7/46
>
> Suggested-by: Joe Perches <joe@perches.com>
> Signed-off-by: Nishad Kamdar <nishadkamdar@gmail.com>
Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>
Thanks and regards,
Lokesh
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] firmware: ti_sci: Use the correct style for SPDX License Identifier
2019-06-14 13:57 [PATCH] firmware: ti_sci: Use the correct style for SPDX License Identifier Nishad Kamdar
2019-06-14 14:53 ` Lokesh Vutla
@ 2019-06-19 4:35 ` santosh.shilimkar
1 sibling, 0 replies; 3+ messages in thread
From: santosh.shilimkar @ 2019-06-19 4:35 UTC (permalink / raw)
To: Nishad Kamdar, Nishanth Menon, Tero Kristo, Santosh Shilimkar
Cc: Greg Kroah-Hartman, Joe Perches, Uwe Kleine-König,
linux-arm-kernel, linux-kernel
On 6/14/19 6:57 AM, Nishad Kamdar wrote:
> This patch corrects the SPDX License Identifier style
> in header file related to Firmware Drivers for Texas
> Instruments SCI Protocol.
> For C header files Documentation/process/license-rules.rst
> mandates C-like comments (opposed to C source files where
> C++ style should be used)
>
> Changes made by using a script provided by Joe Perches here:
> https://lkml.org/lkml/2019/2/7/46
>
> Suggested-by: Joe Perches <joe@perches.com>
> Signed-off-by: Nishad Kamdar <nishadkamdar@gmail.com>
> ---
Applied
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-06-19 4:35 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-14 13:57 [PATCH] firmware: ti_sci: Use the correct style for SPDX License Identifier Nishad Kamdar
2019-06-14 14:53 ` Lokesh Vutla
2019-06-19 4:35 ` santosh.shilimkar
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).