From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Piotr Maziarz <piotrx.maziarz@linux.intel.com>,
linux-kernel@vger.kernel.org, mingo@redhat.com,
andriy.shevchenko@intel.com, gustaw.lewandowski@intel.com
Subject: Re: [PATCH v2 1/2] seq_buf: Add printing formatted hex dumps
Date: Thu, 14 Nov 2019 09:00:40 +0100 [thread overview]
Message-ID: <8d937230-9890-aabc-b268-c3a2e1f799b0@intel.com> (raw)
In-Reply-To: <20191113160237.6b8efe12@gandalf.local.home>
On 2019-11-13 22:02, Steven Rostedt wrote:
> On Thu, 7 Nov 2019 13:45:37 +0100
> Piotr Maziarz <piotrx.maziarz@linux.intel.com> wrote:
>
>> Provided function is an analogue of print_hex_dump().
>>
>> Implementing this function in seq_buf allows using for multiple
>> purposes (e.g. for tracing) and therefore prevents from code duplication
>> in every layer that uses seq_buf.
>>
>> print_hex_dump() is an essential part of logging data to dmesg. Adding
>> similar capability for other purposes is beneficial to all users.
>>
>> Example usage:
>> seq_buf_hex_dump(seq, "", DUMP_PREFIX_OFFSET, 16, 4, buf,
>> ARRAY_SIZE(buf), true);
>> Example output:
>> 00000000: 00000000 ffffff10 ffffff32 ffff3210 ........2....2..
>> 00000010: ffff3210 83d00437 c0700000 00000000 .2..7.....p.....
>> 00000020: 02010004 0000000f 0000000f 00004002 .............@..
>> 00000030: 00000fff 00000000 ........
>>
>> Signed-off-by: Piotr Maziarz <piotrx.maziarz@linux.intel.com>
>> Signed-off-by: Cezary Rojewski <cezary.rojewski@intel.com>
>
> I'm curious about the two signed off bys? Was Cezary a co-author?
>
Hello Steven,
Code is done by Piotr. I merely took part in shaping this idea and doing
initial reviews. Kudos to Andy for helping us out here.
As a dev lead and maintainer for Intel ASoC team, patches coming from my
team are also being signed off me so any reviewer has a person to
complain to in case of any issues for extended period of time.
Czarek
next prev parent reply other threads:[~2019-11-14 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 12:45 Piotr Maziarz
2019-11-07 12:45 ` [PATCH v2 2/2] tracing: Use seq_buf_hex_dump() to dump buffers Piotr Maziarz
2019-11-13 21:09 ` Steven Rostedt
2019-11-26 14:53 ` Piotr Maziarz
2019-11-26 19:51 ` Steven Rostedt
2019-11-27 10:56 ` Piotr Maziarz
2019-11-13 21:02 ` [PATCH v2 1/2] seq_buf: Add printing formatted hex dumps Steven Rostedt
2019-11-14 8:00 ` Cezary Rojewski [this message]
2019-11-14 14:35 ` Steven Rostedt
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=8d937230-9890-aabc-b268-c3a2e1f799b0@intel.com \
--to=cezary.rojewski@intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=gustaw.lewandowski@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=piotrx.maziarz@linux.intel.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®