From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Thomas Wood <thomas.wood@intel.com>
Subject: Re: [PATCH 0/2] intel_reg: Intel graphics register multitool
Date: Wed, 15 Apr 2015 13:23:16 +0300 [thread overview]
Message-ID: <87h9shsnaj.fsf@intel.com> (raw)
In-Reply-To: <cover.1429092573.git.jani.nikula@intel.com>
On Wed, 15 Apr 2015, Jani Nikula <jani.nikula@intel.com> wrote:
> Hi all, this is v1 after the RFC [1], with polish applied and too many
> small changes to list. Go ahead and play with it!
Thomas, sorry for missing i-g-t in the subject; apparently git
send-email won't add it regardless of the --subject-prefix if the
patches were already produced with git format-patch.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-04-15 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 10:15 [PATCH 0/2] intel_reg: Intel graphics register multitool Jani Nikula
2015-04-15 10:15 ` [PATCH 1/2] intel_reg: introduce one intel_reg tool to rule them all Jani Nikula
2015-04-15 10:15 ` [PATCH 2/2] man: add man page for intel_reg in rst format Jani Nikula
2015-04-16 16:10 ` Thomas Wood
2015-04-15 10:23 ` Jani Nikula [this message]
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=87h9shsnaj.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.wood@intel.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