All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Thomas Wood <thomas.wood@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] tools: print a warning for tools replaced by intel_reg
Date: Mon, 15 Jun 2015 18:12:16 +0200	[thread overview]
Message-ID: <20150615161216.GF23637@phenom.ffwll.local> (raw)
In-Reply-To: <CANkqdn3Bi6xEMP7GfexvHhDV+K_JZOoXHyv85Bm4hSfNcsFgbg@mail.gmail.com>

On Mon, Jun 15, 2015 at 04:58:51PM +0100, Thomas Wood wrote:
> On 15 June 2015 at 16:51, Jani Nikula <jani.nikula@intel.com> wrote:
> > On Mon, 15 Jun 2015, Daniel Vetter <daniel@ffwll.ch> wrote:
> >> On Wed, Jun 10, 2015 at 11:41:03AM +0100, Thomas Wood wrote:
> >>> Cc: Jani Nikula <jani.nikula@intel.com>
> >>> Signed-off-by: Thomas Wood <thomas.wood@intel.com>
> >>
> >> I'd go even one step further and do an exec using the corresponding
> >> intel_reg commandline. On top of this patch ofc.
> >
> > IMO more work than it's worth.
> 
> I looked at this, but the output and options of intel_reg don't quite
> match those of tools it is replacing, so it's not an exact
> replacement.
> 
> 
> >
> >> Then we could nuke a lot of the existing boilerplate already and then
> >> perhaps nuke all the tools one release later on or so.
> >
> > Hmm didn't we already make a release with the warnings? I'd just nuke
> > the deprecated ones from git now.
> 
> Yes, the 1.11 release has the warnings.

Ah in that case let's just move ahead and nuke them all.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2015-06-15 16:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 10:41 [PATCH i-g-t] tools: print a warning for tools replaced by intel_reg Thomas Wood
2015-06-15 15:51 ` Daniel Vetter
2015-06-15 15:51   ` Jani Nikula
2015-06-15 15:58     ` Thomas Wood
2015-06-15 16:12       ` Daniel Vetter [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=20150615161216.GF23637@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --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 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.