All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Sean Paul <sean@poorly.run>, Maxime Ripard <mripard@kernel.org>
Cc: dim-tools@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	Andrzej Hajda <a.hajda@samsung.com>,
	Vinay Simha BN <simhavcs@gmail.com>,
	Thierry Reding <treding@nvidia.com>
Subject: Re: [PULL] topic/drm-mipi-dsi-dsc-updates
Date: Wed, 20 Nov 2019 16:04:22 +0200	[thread overview]
Message-ID: <877e3uy789.fsf@intel.com> (raw)
In-Reply-To: <44c6a588-af34-2acd-40b3-b9d82c35226b@linux.intel.com>

On Wed, 20 Nov 2019, Maarten Lankhorst <maarten.lankhorst@linux.intel.com> wrote:
> Op 14-11-2019 om 15:35 schreef Jani Nikula:
>> On Mon, 11 Nov 2019, Jani Nikula <jani.nikula@intel.com> wrote:
>>> Hi Sean, Maarten and Maxime -
>>>
>>> Here's the topic branch about DSI changes as I wrote in [1]. Once you've
>>> pulled this in drm-misc, I'll follow suit in i915.
>> Ping.
>>
>> FWIW Daniel acked the approach on IRC.
>>
>> BR,
>> Jani.
>>
>>
> Pushed, thanks. :)

Thanks; also pulled to drm-intel-next-queued now.

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

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Sean Paul <sean@poorly.run>, Maxime Ripard <mripard@kernel.org>
Cc: dim-tools@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Vinay Simha BN <simhavcs@gmail.com>,
	Thierry Reding <treding@nvidia.com>
Subject: Re: [PULL] topic/drm-mipi-dsi-dsc-updates
Date: Wed, 20 Nov 2019 16:04:22 +0200	[thread overview]
Message-ID: <877e3uy789.fsf@intel.com> (raw)
Message-ID: <20191120140422.qb0Tre0eDVX7gPi2cW3tO206jpdmcuofBEEltoNdKhE@z> (raw)
In-Reply-To: <44c6a588-af34-2acd-40b3-b9d82c35226b@linux.intel.com>

On Wed, 20 Nov 2019, Maarten Lankhorst <maarten.lankhorst@linux.intel.com> wrote:
> Op 14-11-2019 om 15:35 schreef Jani Nikula:
>> On Mon, 11 Nov 2019, Jani Nikula <jani.nikula@intel.com> wrote:
>>> Hi Sean, Maarten and Maxime -
>>>
>>> Here's the topic branch about DSI changes as I wrote in [1]. Once you've
>>> pulled this in drm-misc, I'll follow suit in i915.
>> Ping.
>>
>> FWIW Daniel acked the approach on IRC.
>>
>> BR,
>> Jani.
>>
>>
> Pushed, thanks. :)

Thanks; also pulled to drm-intel-next-queued now.

BR,
Jani.


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

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Sean Paul <sean@poorly.run>, Maxime Ripard <mripard@kernel.org>
Cc: dim-tools@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	Andrzej Hajda <a.hajda@samsung.com>,
	Vinay Simha BN <simhavcs@gmail.com>,
	Thierry Reding <treding@nvidia.com>
Subject: Re: [Intel-gfx] [PULL] topic/drm-mipi-dsi-dsc-updates
Date: Wed, 20 Nov 2019 16:04:22 +0200	[thread overview]
Message-ID: <877e3uy789.fsf@intel.com> (raw)
Message-ID: <20191120140422.5NgYSJ9Xszy9g3HFa7yrd92AxZAazkC_hc1oFIESHkQ@z> (raw)
In-Reply-To: <44c6a588-af34-2acd-40b3-b9d82c35226b@linux.intel.com>

On Wed, 20 Nov 2019, Maarten Lankhorst <maarten.lankhorst@linux.intel.com> wrote:
> Op 14-11-2019 om 15:35 schreef Jani Nikula:
>> On Mon, 11 Nov 2019, Jani Nikula <jani.nikula@intel.com> wrote:
>>> Hi Sean, Maarten and Maxime -
>>>
>>> Here's the topic branch about DSI changes as I wrote in [1]. Once you've
>>> pulled this in drm-misc, I'll follow suit in i915.
>> Ping.
>>
>> FWIW Daniel acked the approach on IRC.
>>
>> BR,
>> Jani.
>>
>>
> Pushed, thanks. :)

Thanks; also pulled to drm-intel-next-queued now.

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

  reply	other threads:[~2019-11-20 14:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-11 15:25 [PULL] topic/drm-mipi-dsi-dsc-updates Jani Nikula
2019-11-11 15:25 ` [Intel-gfx] " Jani Nikula
2019-11-11 15:25 ` Jani Nikula
2019-11-14 14:35 ` Jani Nikula
2019-11-14 14:35   ` [Intel-gfx] " Jani Nikula
2019-11-14 14:35   ` Jani Nikula
2019-11-20 13:16   ` Maarten Lankhorst
2019-11-20 13:16     ` [Intel-gfx] " Maarten Lankhorst
2019-11-20 14:04     ` Jani Nikula [this message]
2019-11-20 14:04       ` Jani Nikula
2019-11-20 14:04       ` Jani Nikula

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=877e3uy789.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=a.hajda@samsung.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 \
    --cc=sean@poorly.run \
    --cc=simhavcs@gmail.com \
    --cc=treding@nvidia.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 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.