From: metux <metux@gmx.de>
To: Ira Weiny <ira.weiny@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: Fan Ni <fan.ni@samsung.com>, Bagas Sanjaya <bagasdotme@gmail.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-cxl@vger.kernel.org
Subject: Re: [PATCH v2 0/4] printf: Add struct range print specifier
Date: Wed, 30 Oct 2024 11:51:54 +0100 [thread overview]
Message-ID: <18854680-4ab7-4453-85ff-78351d4d4ec9@gmx.de> (raw)
In-Reply-To: <20241025-cxl-pra-v2-0-123a825daba2@intel.com>
On 26.10.24 02:46, Ira Weiny wrote:
> Support for the Compute Express Link (CXL) Dynamic Capacity Devices
> (DCD) have grown a number of uses to print struct range.[1] Support for
> a printf specifier '%pra' was being worked within a large series and has
> garnered a number of comments and discussion.
This is just printing out hex dump of a memory range, correct ?
What I'm looking for quite some time is a sane way for dumping structs
in a human readable form (field: value pairs, using their actual types
eg. int vs string, ...).
Any idea to do that in a generic way ?
(potentially using debug info ?)
--mtx
next prev parent reply other threads:[~2024-10-30 10:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 0:46 [PATCH v2 0/4] printf: Add struct range print specifier Ira Weiny
2024-10-26 0:46 ` [PATCH v2 1/4] test printf: Add very basic struct resource tests Ira Weiny
2024-10-28 9:07 ` Andy Shevchenko
2024-10-28 21:29 ` Ira Weiny
2024-10-26 0:46 ` [PATCH v2 2/4] Documentation/printf: struct resource add start == end special case Ira Weiny
2024-10-28 9:07 ` Andy Shevchenko
2024-10-29 15:19 ` Jonathan Cameron
2024-11-07 12:34 ` Petr Mladek
2024-10-26 0:46 ` [PATCH v2 3/4] printf: Add print format (%pra) for struct range Ira Weiny
2024-10-28 9:11 ` Andy Shevchenko
2024-11-07 14:24 ` Petr Mladek
2024-10-26 0:46 ` [PATCH v2 4/4] cxl/cdat: Use %pra for dpa range outputs Ira Weiny
2024-10-30 10:51 ` metux [this message]
2024-10-31 21:34 ` [PATCH v2 0/4] printf: Add struct range print specifier Ira Weiny
2024-11-07 14:43 ` Petr Mladek
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=18854680-4ab7-4453-85ff-78351d4d4ec9@gmx.de \
--to=metux@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=vishal.l.verma@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