From: Dylan Yudaken <[email protected]>
To: "[email protected]" <[email protected]>,
"[email protected]" <[email protected]>
Cc: Kernel Team <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [PATCH v2 0/4] io_uring: text representation of opcode in trace
Date: Tue, 26 Apr 2022 08:16:48 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Mon, 2022-04-25 at 16:47 -0600, Jens Axboe wrote:
> On 4/25/22 9:07 AM, Dylan Yudaken wrote:
> >
> > This series adds the text representation of opcodes into the trace.
> > This
> > makes it much quicker to understand traces without having to
> > translate
> > opcodes in your head.
> >
> > Patch 1 adds a type to io_uring opcodes
> > Patch 2 is the translation function.
> > Patch 3 is a small cleanup
> > Patch 4 uses the translator in the trace logic
>
> Sorry forgot, one last request - can you make this against the
> for-5.19/io_uring-socket branch? That'll include the opcodes added
> for
> 5.19, otherwise we'll most likely end up in a situation where it'll
> merge cleanly but trigger a warning at build time. Also avoids having
> to
> fix those up after the fact in any case.
>
Sure - that's easy enough
prev parent reply other threads:[~2022-04-26 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 15:07 [PATCH v2 0/4] io_uring: text representation of opcode in trace Dylan Yudaken
2022-04-25 15:07 ` [PATCH v2 1/4] io_uring: add type to op enum Dylan Yudaken
2022-04-25 15:07 ` [PATCH v2 2/4] io_uring: add io_uring_get_opcode Dylan Yudaken
2022-04-25 15:07 ` [PATCH v2 3/4] io_uring: rename op -> opcode Dylan Yudaken
2022-04-25 15:07 ` [PATCH v2 4/4] io_uring: use the text representation of ops in trace Dylan Yudaken
2022-04-25 22:47 ` [PATCH v2 0/4] io_uring: text representation of opcode " Jens Axboe
2022-04-26 8:16 ` Dylan Yudaken [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=09bb847c0557e89432d1d3a24cd46d82d0f4c04d.camel@fb.com \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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