From: Cyril Brulebois <kibi@debian.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] Avoid calling xf86nameCompare() with a NULL pointer.
Date: Tue, 12 Jun 2012 22:30:27 +0200 [thread overview]
Message-ID: <20120612203027.GA24509@mraw.org> (raw)
In-Reply-To: <1339532296_13140@CP5-2952>
[-- Attachment #1.1: Type: text/plain, Size: 155 bytes --]
Chris Wilson <chris@chris-wilson.co.uk> (12/06/2012):
> Pushed with only a slightly different colour of paint. Thanks,
> -Chris
Cake? Yummy!
Mraw,
KiBi.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 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:[~2012-06-12 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 18:15 [PATCH] Avoid calling xf86nameCompare() with a NULL pointer Cyril Brulebois
2012-06-12 20:18 ` Chris Wilson
2012-06-12 20:30 ` Cyril Brulebois [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=20120612203027.GA24509@mraw.org \
--to=kibi@debian.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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