From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] lib: Add a YAML emitter
Date: Fri, 14 Feb 2020 09:57:09 +0200 [thread overview]
Message-ID: <87h7zt61pm.fsf@intel.com> (raw)
In-Reply-To: <20200213232338.3746869-1-chris@chris-wilson.co.uk>
On Thu, 13 Feb 2020, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Provide a library to generate correct YAML for use in structured debugfs
> or similar information dumps. This will be useful to pull our large
> information dumps into a forwards compatible, parse-able file-format by
> forcing some structure upon ourselves!
Acked-by: Jani Nikula <jani.nikula@intel.com>
I like the idea. I like the prospect of converting *all* of our bigger
debugfs files to have some structure. Why not smaller ones too, to be
uniform. Not entirely sold on using it in sysfs, like the example code
did, but even that might be justified for capturing a state.
For many things I do like json, but yaml is definitely more human
readable as-is and more suitable for debugfs.
I expect the biggest uphill to be merging the bulk of stuff to
lib/. It's a lot of code in one go.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-02-14 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 23:23 [Intel-gfx] [PATCH] lib: Add a YAML emitter Chris Wilson
2020-02-14 0:13 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-02-14 1:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-02-14 7:57 ` Jani Nikula [this message]
2020-02-14 12:48 ` [Intel-gfx] [PATCH] " Chris Wilson
2020-02-17 15:48 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " Patchwork
2021-02-11 11:38 [Intel-gfx] [PATCH] " Chris Wilson
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=87h7zt61pm.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).