All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>,
	Dave Airlie <airlied@linux.ie>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Keith Packard <keithp@keithp.com>,
	Haneen Mohammed <hamohammed.sa@gmail.com>,
	Sean Paul <seanpaul@chromium.org>
Subject: linux-next: manual merge of the drm-misc tree with the drm tree
Date: Wed, 1 Nov 2017 14:36:52 +1100	[thread overview]
Message-ID: <20171101143652.409620ca@canb.auug.org.au> (raw)

Hi all,

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

  include/drm/drmP.h

between commit:

  e7646f84ad4f ("drm: Add new LEASE debug level")

from the drm tree and commit:

  02c9656b2f0d ("drm: Move debug macros out of drmP.h")

from the drm-misc tree.

I fixed it up (I used the drm-misc version of the file and added the below
merge fix patch) 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.

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Wed, 1 Nov 2017 14:33:07 +1100
Subject: [PATCH] drm-misc: merge fix up for DEBUG printing macros move

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 include/drm/drm_print.h | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/include/drm/drm_print.h b/include/drm/drm_print.h
index 7b9c86a6ca3e..edcea83a5050 100644
--- a/include/drm/drm_print.h
+++ b/include/drm/drm_print.h
@@ -171,6 +171,7 @@ static inline struct drm_printer drm_debug_printer(const char *prefix)
 #define DRM_UT_ATOMIC		0x10
 #define DRM_UT_VBL		0x20
 #define DRM_UT_STATE		0x40
+#define DRM_UT_LEASE		0x80
 
 __printf(6, 7)
 void drm_dev_printk(const struct device *dev, const char *level,
@@ -287,6 +288,9 @@ void drm_printk(const char *level, unsigned int category,
 #define DRM_DEBUG_VBL(fmt, ...)					\
 	drm_printk(KERN_DEBUG, DRM_UT_VBL, fmt, ##__VA_ARGS__)
 
+#define DRM_DEBUG_LEASE(fmt, ...)					\
+	drm_printk(KERN_DEBUG, DRM_UT_LEASE, fmt, ##__VA_ARGS__)
+
 #define _DRM_DEV_DEFINE_DEBUG_RATELIMITED(dev, level, fmt, args...)	\
 ({									\
 	static DEFINE_RATELIMIT_STATE(_rs,				\


-- 
Cheers,
Stephen Rothwell

             reply	other threads:[~2017-11-01  3:36 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01  3:36 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-09 23:54 linux-next: manual merge of the drm-misc tree with the drm tree Stephen Rothwell
2022-11-09 23:54 ` Stephen Rothwell
2019-10-09  0:12 Stephen Rothwell
2019-10-09  0:10 Stephen Rothwell
2019-10-09  0:10 ` Stephen Rothwell
2019-10-08 23:46 Stephen Rothwell
2019-10-08 23:46 ` Stephen Rothwell
2019-10-08 23:38 Stephen Rothwell
2019-10-08 23:38 ` Stephen Rothwell
2019-10-08 23:33 Stephen Rothwell
2019-08-19  3:18 Stephen Rothwell
2019-06-11  3:52 Stephen Rothwell
2019-06-11  3:52 ` Stephen Rothwell
2019-06-11  3:38 Stephen Rothwell
2019-06-11  3:38 ` Stephen Rothwell
2019-04-09  1:34 Stephen Rothwell
2019-04-09  1:34 ` Stephen Rothwell
2019-04-09  7:23 ` Gerd Hoffmann
2019-02-08  1:27 Stephen Rothwell
2019-02-08  8:53 ` Daniel Vetter
2019-02-08  8:53   ` Daniel Vetter
2019-02-08  9:25   ` Stephen Rothwell
2019-02-08  9:34     ` Daniel Vetter
2018-11-23  0:13 Stephen Rothwell
2018-11-23  0:13 ` Stephen Rothwell
2018-09-18  1:31 Stephen Rothwell
2018-09-12  0:39 Stephen Rothwell
2018-03-19  1:29 Stephen Rothwell
2018-03-19  1:29 ` Stephen Rothwell
2018-03-19 14:14 ` Ville Syrjälä
2017-04-03  3:18 Stephen Rothwell
2017-04-03  3:18 ` Stephen Rothwell
2016-09-28  2:11 Stephen Rothwell
2014-12-10  1:49 Stephen Rothwell
2014-12-10  1:49 ` Stephen Rothwell
2014-12-03  2:43 Stephen Rothwell
2014-12-03  2:43 ` Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171101143652.409620ca@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hamohammed.sa@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=keithp@keithp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=seanpaul@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.