Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Wambui Karuga <wambui.karugax@gmail.com>,
	joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
	airlied@linux.ie, daniel@ffwll.ch
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 00/12] drm/i915/display: convert to drm_device based logging macros.
Date: Tue, 11 Feb 2020 16:09:21 +0200	[thread overview]
Message-ID: <87ftfhz04u.fsf@intel.com> (raw)
In-Reply-To: <20200206080014.13759-1-wambui.karugax@gmail.com>

On Thu, 06 Feb 2020, Wambui Karuga <wambui.karugax@gmail.com> wrote:
> This patchset continues the conversion of the printk based drm logging
> macros in drm/i915 to use the struct drm_device based logging macros.
> This series was done both using coccinelle and manually.

Thank you for the patches! I pushed all the patches that I did *not*
reply to separately.

BR,
Jani.

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

      parent reply	other threads:[~2020-02-11 14:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06  8:00 [Intel-gfx] [PATCH v2 00/12] drm/i915/display: convert to drm_device based logging macros Wambui Karuga
2020-02-06  8:00 ` [Intel-gfx] [PATCH v2 01/12] drm/i915/dp: convert to struct " Wambui Karuga
2020-02-11 14:03   ` Jani Nikula
2020-02-06  8:00 ` [Intel-gfx] [PATCH v2 02/12] drm/i915/dp_link_training: convert to " Wambui Karuga
2020-02-06  8:00 ` [Intel-gfx] [PATCH v2 03/12] drm/i915/atomic: conversion " Wambui Karuga
2020-02-06  8:00 ` [Intel-gfx] [PATCH v2 04/12] drm/i915/color: " Wambui Karuga
2020-02-06  8:00 ` [Intel-gfx] [PATCH v2 05/12] drm/i915/crt: automatic " Wambui Karuga
2020-02-06  8:00 ` [Intel-gfx] [PATCH v2 06/12] drm/i915/dp_aux_backlight: convert " Wambui Karuga
2020-02-11 14:08   ` Jani Nikula
2020-02-06  8:00 ` [Intel-gfx] [PATCH v2 07/12] drm/i915/dpll_mgr: " Wambui Karuga
2020-02-06  8:00 ` [Intel-gfx] [PATCH v2 08/12] drm/i915/combo_phy: convert to struct drm_device " Wambui Karuga
2020-02-06  8:00 ` [Intel-gfx] [PATCH v2 09/12] drm/i915/dp_mst: convert to drm_device based " Wambui Karuga
2020-02-11 14:05   ` Jani Nikula
2020-02-06  8:00 ` [Intel-gfx] [PATCH v2 10/12] drm/i915/dsi_vbt: " Wambui Karuga
2020-02-06  8:00 ` [Intel-gfx] [PATCH v2 11/12] drm/i915/hdmi: convert to struct " Wambui Karuga
2020-02-11 13:47   ` Jani Nikula
2020-02-11 18:04     ` Wambui Karuga
2020-02-06  8:00 ` [Intel-gfx] [PATCH v2 12/12] drm/i915/dpio_phy: convert to " Wambui Karuga
2020-02-06  8:38 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display: " Patchwork
2020-02-06  9:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-02-09  1:11 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-02-11 14:09 ` Jani Nikula [this message]

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=87ftfhz04u.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=wambui.karugax@gmail.com \
    /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