[lkml]   [2019]   [Jun]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectlinux-next: manual merge of the clockevents tree with Linus' tree
Hi all,

Today's linux-next merge of the clockevents tree got a conflict in:


between commit:

9c92ab619141 ("treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 282")

from Linus' tree and commit:

75e9f7c6dca8 ("clocksource/drivers/tegra: Use SPDX identifier")

from the clockevents tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

Stephen Rothwell

diff --cc drivers/clocksource/timer-tegra.c
index 1e7ece279730,9406855781ff..000000000000
--- a/drivers/clocksource/timer-tegra.c
+++ b/drivers/clocksource/timer-tegra.c
@@@ -1,11 -1,11 +1,11 @@@
-// SPDX-License-Identifier: GPL-2.0
+// SPDX-License-Identifier: GPL-2.0-only
* Copyright (C) 2010 Google, Inc.
- *
- * Author:
- * Colin Cross <>
+ * Author: Colin Cross <>

+ #define pr_fmt(fmt) "tegra-timer: " fmt
#include <linux/clk.h>
#include <linux/clockchips.h>
#include <linux/cpu.h>
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2019-06-11 07:24    [W:0.029 / U:11.656 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site