From: Thomas Hellstrom <thellstrom@vmware.com>
To: airlied@gmail.com, Dave Airlie <airlied@redhat.com>
Cc: Thomas Hellstrom <thellstrom@vmware.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH -fixes 0/3][RESEND] Documentation updates
Date: Thu, 15 Dec 2011 13:30:43 +0100 [thread overview]
Message-ID: <4EE9E873.30005@vmware.com> (raw)
In-Reply-To: <1321877318-10570-1-git-send-email-thellstrom@vmware.com>
Dave,
Please pull this series into drm-fixes for 3.2.
Thanks,
Thomas
On 11/21/2011 01:08 PM, Thomas Hellstrom wrote:
> A couple of updates to various interface docs
>
> In-Reply-To:
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
>
prev parent reply other threads:[~2011-12-15 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 12:08 [PATCH -fixes 0/3] Documentation updates Thomas Hellstrom
2011-11-21 12:08 ` [PATCH 1/3] drm: Update the DRM_IOCTL_MODE_CURSOR documentation Thomas Hellstrom
2011-11-21 12:08 ` [PATCH 2/3] drm: Update the pageflip ioctl documentation Thomas Hellstrom
2011-11-21 12:08 ` [PATCH 3/3] ttm: Update move_notify and swap_notify documentation Thomas Hellstrom
2011-12-15 12:30 ` Thomas Hellstrom [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=4EE9E873.30005@vmware.com \
--to=thellstrom@vmware.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.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