From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-15?Q?Thomas_B=E4chler?= Subject: Re: [PATCH 1/4] introduce intel_ring_buffer structure Date: Sat, 08 May 2010 20:15:08 +0200 Message-ID: <4BE5AA2C.1040907@archlinux.org> References: <1273108805-1354-1-git-send-email-nanhai.zou@intel.com> <87d3x775w8.fsf@pollan.anholt.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1910687983==" Return-path: Received: from archlinux.org (gerolde.archlinux.org [66.211.214.132]) by gabe.freedesktop.org (Postfix) with ESMTP id 504BE9E775 for ; Sat, 8 May 2010 11:15:11 -0700 (PDT) In-Reply-To: <87d3x775w8.fsf@pollan.anholt.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Eric Anholt Cc: Intel GFX List-Id: intel-gfx@lists.freedesktop.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============1910687983== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enigE371C6DD7644AB0834239985" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE371C6DD7644AB0834239985 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Am 07.05.2010 23:34, schrieb Eric Anholt: > On Thu, 6 May 2010 09:20:02 +0800, Zou Nan hai = wrote: >> introduce intel_ring_buffer structure. >> sequential number, IRQ logic and hardware status page >> were included in the intel_ring_buffer structure >=20 > I tried to go apply this patch series once again. The first one > actually applies now. The second produces massive rejects, whether I a= pply > against linus master or drm-intel-next. >=20 > 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. --------------enigE371C6DD7644AB0834239985 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkvlqiwACgkQEda5KzHP/VBD6wCeOIPxWCbDwYFsID7gc7eaFcqB sykAnRVJ/J+e78MBupeC2AtFuvbJI/2w =dXwH -----END PGP SIGNATURE----- --------------enigE371C6DD7644AB0834239985-- --===============1910687983== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx --===============1910687983==--