From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Wambui Karuga <wambui.karugax@gmail.com>
Subject: Re: [Intel-gfx] [PATCH 00/10] drm/i915/display: conversion to drm_device based logging macros
Date: Wed, 11 Mar 2020 12:50:46 +0200 [thread overview]
Message-ID: <87o8t3kvw9.fsf@intel.com> (raw)
In-Reply-To: <87blp5o8yx.fsf@intel.com>
On Mon, 09 Mar 2020, Jani Nikula <jani.nikula@intel.com> wrote:
> Please ignore this, I seem to have some smtp trouble which fails some of
> tha patches. This will be incomplete.
>
> Wambui, I'll resend this later.
Okay, I sent them with the same message-ids, so the patches amended this
beginning of the series.
I pushed all the patches that I didn't change. Please double check the
below patches that I adjusted, so I can push them.
>> drm/i915/fbc: convert to drm_device based logging macros.
>> drm/i915/fbdev: convert to drm_device based logging.
>> drm/i915/hdcp: convert to struct drm_device based logging.
Thanks,
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
next prev parent reply other threads:[~2020-03-11 10:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 15:12 [Intel-gfx] [PATCH 00/10] drm/i915/display: conversion to drm_device based logging macros Jani Nikula
2020-03-09 15:12 ` [Intel-gfx] [PATCH 01/10] drm/i915/dsb: convert " Jani Nikula
2020-03-10 8:52 ` Jani Nikula
2020-03-09 15:15 ` [Intel-gfx] [PATCH 00/10] drm/i915/display: conversion " Jani Nikula
2020-03-11 10:50 ` Jani Nikula [this message]
2020-03-11 14:56 ` Wambui Karuga
2020-03-18 19:10 ` Jani Nikula
2020-03-10 8:52 ` Jani Nikula
2020-03-10 8:52 ` [Intel-gfx] [PATCH 02/10] drm/i915/fbc: convert " Jani Nikula
2020-03-18 14:43 ` Wambui Karuga
2020-03-10 8:52 ` [Intel-gfx] [PATCH 03/10] drm/i915/fbdev: convert to drm_device based logging Jani Nikula
2020-03-18 14:45 ` Wambui Karuga
2020-03-10 8:52 ` [Intel-gfx] [PATCH 04/10] drm/i915/fifo_underrun: " Jani Nikula
2020-03-10 8:52 ` [Intel-gfx] [PATCH 05/10] drm/i915/gmbus: convert to drm_device based logging, Jani Nikula
2020-03-10 8:52 ` [Intel-gfx] [PATCH 06/10] drm/i915/hdcp: convert to struct drm_device based logging Jani Nikula
2020-03-18 14:46 ` Wambui Karuga
2020-03-10 8:52 ` [Intel-gfx] [PATCH 07/10] drm/i915/hotplug: convert to " Jani Nikula
2020-03-10 8:52 ` [Intel-gfx] [PATCH 08/10] drm/i915/lpe_audio: convert to drm_device based logging macros Jani Nikula
2020-03-10 8:52 ` [Intel-gfx] [PATCH 09/10] drm/i915/lvds: " Jani Nikula
2020-03-10 8:52 ` [Intel-gfx] [PATCH 10/10] drm/i915/overlay: convert to drm_device based logging Jani Nikula
2020-03-10 17:33 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display: conversion to drm_device based logging macros (rev6) Patchwork
2020-03-10 17:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-03-10 22:39 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2020-02-26 10:11 [Intel-gfx] [PATCH 00/10] drm/i915/display: conversion to drm_device based logging macros Wambui Karuga
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=87o8t3kvw9.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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