From: Eric Anholt <eric@anholt.net>
To: Peter Clifton <pcjc2@cam.ac.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] Fix out of tree builds broken by i915/i915_trace_points.c
Date: Sun, 02 May 2010 11:18:18 -0700 [thread overview]
Message-ID: <877hnmdv6d.fsf@pollan.anholt.net> (raw)
In-Reply-To: <1271884032.20195.1.camel@pcjc2lap>
[-- Attachment #1.1: Type: text/plain, Size: 339 bytes --]
On Wed, 21 Apr 2010 22:07:12 +0100, Peter Clifton <pcjc2@cam.ac.uk> wrote:
> Patch attached.
Please include a Signed-off-by indicating agreement with
Documentation/SubmittingPatches: so I can apply it to the kernel. Also,
git send-email instead of attachments makes it so I don't have to
hand-edit your commit messages after applying :)
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2010-05-02 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 21:07 [PATCH] Fix out of tree builds broken by i915/i915_trace_points.c Peter Clifton
2010-05-02 18:18 ` Eric Anholt [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=877hnmdv6d.fsf@pollan.anholt.net \
--to=eric@anholt.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=pcjc2@cam.ac.uk \
/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