From: Jani Nikula <jani.nikula@linux.intel.com>
To: Sean Paul <seanpaul@chromium.org>, Hans Verkuil <hverkuil@xs4all.nl>
Cc: "DRM maintainer tools announcements, discussion,
and development" <dim-tools@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PULL] drm/i915: Add HDCP support to i915
Date: Wed, 14 Feb 2018 16:41:14 +0200 [thread overview]
Message-ID: <87y3jv4os5.fsf@intel.com> (raw)
In-Reply-To: <20180214135249.bio6hu3j2hwrhqkt@art_vandelay>
On Wed, 14 Feb 2018, Sean Paul <seanpaul@chromium.org> wrote:
> On Wed, Feb 14, 2018 at 02:48:29PM +0100, Hans Verkuil wrote:
>> Yes, your patches I've seen, but the 12 from Ramalingam I haven't seen.
>> At least not on dri-devel. It's a bit weird.
>
> Ahh, I'm sorry I misunderstood. I think Ram may have sent those to intel-gfx
> exclusively.
We rarely post i915 specific patches to dri-devel, just intel-gfx, but
in cases where they warrant changes in drm core it may be warranted to
add a wider audience. Sorry about failing to do that here.
All the commits have Link: tags back to the patches posted publicly,
with message-ids.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-02-14 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 20:18 [PULL] drm/i915: Add HDCP support to i915 Sean Paul
2018-02-14 8:33 ` Hans Verkuil
2018-02-14 13:44 ` Sean Paul
2018-02-14 13:48 ` Hans Verkuil
2018-02-14 13:52 ` Sean Paul
2018-02-14 14:41 ` 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=87y3jv4os5.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hverkuil@xs4all.nl \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--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.