Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Clifton <pcjc2@cam.ac.uk>
To: Alexander Lam <lambchop468@gmail.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] Graphics corruption issues
Date: Mon, 26 Apr 2010 00:19:52 +0100	[thread overview]
Message-ID: <1272237592.5170.2.camel@pcjc2lap> (raw)
In-Reply-To: <i2vdfb03c971004251554sa0c0f38fod279ef5970b1902a@mail.gmail.com>

On Sun, 2010-04-25 at 18:54 -0400, Alexander Lam wrote:
> Oh my bad. *facepalm*
> I didn't see that you had already posted them inline.

They were attached, with a suggested viewing hint of inline - so I think
your original comment was correct.

I'm not familiar with how to send mails straight from git, and I thought
non-attached versions of the patch pasted into my mail client
(evolution) would be more likely to produce a corrupt patch, munging
tabs, spaces etc..

Thanks for your comments and testing though. I'm not entirely sure if
returning FALSE when pixman can't do a blit is sufficient, but it "seems
to help" here. Perhaps Chris can comment.

-- 
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)

  parent reply	other threads:[~2010-04-25 23:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 18:19 [PATCH] Graphics corruption issues Peter Clifton
     [not found] ` <o2ldfb03c971004251552k55defa42q5962b1f74f9f8630@mail.gmail.com>
     [not found]   ` <i2vdfb03c971004251554sa0c0f38fod279ef5970b1902a@mail.gmail.com>
2010-04-25 23:19     ` Peter Clifton [this message]
2010-04-25 23:23   ` Peter Clifton

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=1272237592.5170.2.camel@pcjc2lap \
    --to=pcjc2@cam.ac.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lambchop468@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox