From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Dave Airlie <airlied@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm: Print pretty names for pixel formats
Date: Fri, 7 Jun 2013 23:35:09 +0300 [thread overview]
Message-ID: <20130607203509.GW5004@intel.com> (raw)
In-Reply-To: <CAPM=9tw3xbei5QemFJGMmx4OcnwSVopo2ZZj9SEPaqMsDf6rog@mail.gmail.com>
On Sat, Jun 08, 2013 at 06:09:42AM +1000, Dave Airlie wrote:
> On Sat, Jun 8, 2013 at 1:43 AM, <ville.syrjala@linux.intel.com> wrote:
> > From: Foo Bar <foo@bar.com>
>
> ^ ??
>
> git config error?
Whoops. Sorry about that. I created the original patch on a test
machine where I apparently had been too lazy to set up my git
correctly. And then I used suppress-cc=author to avoid spamming
myself too much, so I didn't notice it when sending the mail.
Do you want a fixed patch, or will you take care of it on your end?
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-06-07 20:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 15:43 [PATCH 1/4] drm: Print pretty names for pixel formats ville.syrjala
2013-06-07 15:43 ` [PATCH 2/4] drm/i915: " ville.syrjala
2013-06-07 15:43 ` [PATCH 3/4] fb: Make fb_get_options() 'name' parameter const ville.syrjala
2013-06-07 15:43 ` ville.syrjala
2013-06-10 14:22 ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-10 14:22 ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-07 15:43 ` [PATCH 4/4] drm: Constify the pretty-print functions ville.syrjala
2013-06-07 16:03 ` Daniel Vetter
2013-06-19 0:53 ` Laurent Pinchart
2013-06-19 1:36 ` Dave Airlie
2013-06-07 20:09 ` [PATCH 1/4] drm: Print pretty names for pixel formats Dave Airlie
2013-06-07 20:35 ` Ville Syrjälä [this message]
2013-06-07 21:33 ` Dave Airlie
2013-06-10 8:15 ` [PATCH v2] " ville.syrjala
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=20130607203509.GW5004@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.