From: "Thomas Bächler" <thomas@archlinux.org>
To: Eric Anholt <eric.anholt@intel.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/4] introduce intel_ring_buffer structure
Date: Sat, 08 May 2010 20:15:08 +0200 [thread overview]
Message-ID: <4BE5AA2C.1040907@archlinux.org> (raw)
In-Reply-To: <87d3x775w8.fsf@pollan.anholt.net>
[-- Attachment #1.1: Type: text/plain, Size: 796 bytes --]
Am 07.05.2010 23:34, schrieb Eric Anholt:
> On Thu, 6 May 2010 09:20:02 +0800, Zou Nan hai <nanhai.zou@intel.com> wrote:
>> introduce intel_ring_buffer structure.
>> sequential number, IRQ logic and hardware status page
>> were included in the intel_ring_buffer structure
>
> I tried to go apply this patch series once again. The first one
> actually applies now. The second produces massive rejects, whether I apply
> against linus master or drm-intel-next.
>
> Please rebase against drm-intel-next, since that's where it will land.
I'm glad I'm not the only one. I wanted to test the h264 decoding and
actually managed to apply an old version of the first patch - but I also
got the rejects on the second, thought it was my fault though, for using
the wrong tree or so.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 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
next prev parent reply other threads:[~2010-05-08 18:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 1:20 [PATCH 1/4] introduce intel_ring_buffer structure Zou Nan hai
2010-05-06 1:20 ` [PATCH 2/4] convert render engine to use intel_ring_buffer Zou Nan hai
2010-05-06 1:20 ` [PATCH 3/4] add BSD ring buffer support Zou Nan hai
2010-05-06 1:20 ` [PATCH 4/4] adapt intel_ring_buffer into gem Zou Nan hai
2010-05-07 21:34 ` [PATCH 1/4] introduce intel_ring_buffer structure Eric Anholt
2010-05-08 18:15 ` Thomas Bächler [this message]
2010-05-11 22:24 ` Daniel Vetter
2010-05-14 1:39 ` Zou, Nanhai
2010-05-14 9:51 ` Daniel Vetter
2010-05-14 15:03 ` Daniel Vetter
2010-05-17 1:59 ` Zou, Nanhai
2010-05-17 17:52 ` Daniel Vetter
2010-05-14 17:43 ` Owain Ainsworth
2010-05-17 1:43 ` Zou, Nanhai
2010-05-17 17:42 ` Daniel Vetter
2010-05-18 2:20 ` Zou, Nanhai
2010-05-18 16:19 ` Simon Farnsworth
2010-05-19 1:09 ` Zou, Nanhai
2010-05-19 9:00 ` Simon Farnsworth
2010-05-19 16:54 ` Eric Anholt
2010-05-19 17:33 ` Simon Farnsworth
-- strict thread matches above, loose matches on Subject: below --
2010-05-05 3:17 Zou Nan hai
2010-05-05 18:23 ` Daniel Vetter
2010-05-06 2:25 ` Zou, Nanhai
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=4BE5AA2C.1040907@archlinux.org \
--to=thomas@archlinux.org \
--cc=eric.anholt@intel.com \
--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