From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= Subject: Re: [PATCH 02/11] drm/i915: Add SURFLIVE register definitions Date: Thu, 1 Nov 2012 16:23:29 +0200 Message-ID: <20121101142329.GP3791@intel.com> References: <1351698624-26626-1-git-send-email-ville.syrjala@linux.intel.com> <1351698624-26626-3-git-send-email-ville.syrjala@linux.intel.com> <20121031132305.6b3474ed@jbarnes-desktop> <20121031225700.GK5755@phenom.ffwll.local> <20121101141600.GO3791@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by gabe.freedesktop.org (Postfix) with ESMTP id E42F19E828 for ; Thu, 1 Nov 2012 07:23:33 -0700 (PDT) Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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: Daniel Vetter Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Thu, Nov 01, 2012 at 03:19:34PM +0100, Daniel Vetter wrote: > On Thu, Nov 1, 2012 at 3:16 PM, Ville Syrj=E4l=E4 > wrote: > > On Wed, Oct 31, 2012 at 11:57:00PM +0100, Daniel Vetter wrote: > >> On Wed, Oct 31, 2012 at 01:23:05PM -0700, Jesse Barnes wrote: > >> > On Wed, 31 Oct 2012 17:50:15 +0200 > >> > ville.syrjala@linux.intel.com wrote: > >> > > >> > > From: Ville Syrj=E4l=E4 > >> > > > >> > > Signed-off-by: Ville Syrj=E4l=E4 > >> > >> Fails to apply here somehow. Also, this thing is base64 encoded, which > >> confused my normal workflow for a bit ... Dunno what exactly caused th= is > >> havoc. > > > > Strange. I had it sitting on top of drm-intel-next when I sent it. > > > > The whole series seems to be base64 after I got it back from the list. > > Maybe it's out wonderful mail system trying to do something clever. > > Base64 itself shouldn't disturb git-am & co. > = > Yeah, git am coped fine, but patch was a bit upset. I've then feed it > the decoded text/plain part, which resulted in some strange conflicts. > Dunno what has happened there. Can you simply resend a new patch > rebased on top of latest dinq? Will do. -- = Ville Syrj=E4l=E4 Intel OTC