public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
Cc: , dim-tools@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [Intel-gfx] [PULL] topic/drm-warn for drm-misc-next
Date: Wed, 22 Jan 2020 17:25:40 +0200	[thread overview]
Message-ID: <87eevrecnf.fsf@intel.com> (raw)


Hi Maarten/Maxime,

Please pull the drm_device based drm_WARN* macros from the topic
branch. I'll pull the same to drm-intel-next-queued.

I like to use the topic branch here, because due to timing it'll take
forever for the full feature route through drm-next and backmerges.

The baseline was chosen using 'git merge-base drm-misc/drm-misc-next
drm-intel/drm-intel-next-queued'.


BR,
Jani.

The following changes since commit 3cacb2086e41bbdf4a43e494d47d05db356992b9:

  drm/mgag200: Add module parameter to pin all buffers at offset 0 (2020-01-07 11:53:19 +0100)

are available in the Git repository at:

  git://anongit.freedesktop.org/drm/drm-intel tags/topic/drm-warn-2020-01-22

for you to fetch changes up to dc1a73e50f9c63d4dd928df538082200467dc4b1:

  drm/print: introduce new struct drm_device based WARN* macros (2020-01-22 16:17:32 +0200)

----------------------------------------------------------------
struct drm_device based drm_WARN* macros

----------------------------------------------------------------
Pankaj Bharadiya (1):
      drm/print: introduce new struct drm_device based WARN* macros

 include/drm/drm_print.h | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2020-01-22 15:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 15:25 Jani Nikula [this message]
2020-01-23 10:35 ` [Intel-gfx] [PULL] topic/drm-warn for drm-misc-next Maxime Ripard

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=87eevrecnf.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox