From: Olivier Langlois <[email protected]>
To: Pavel Begunkov <[email protected]>,
Jens Axboe <[email protected]>,
Steven Rostedt <[email protected]>,
Ingo Molnar <[email protected]>,
[email protected], [email protected]
Subject: Re: [PATCH] io_uring: Add to traces the req pointer when available
Date: Tue, 25 May 2021 17:29:49 -0400 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Tue, 2021-05-25 at 09:21 +0100, Pavel Begunkov wrote:
>
> Btw, I'd incline you to split it in two patches, a cleanup and one
> adding req, because it's unreadable and hides the real change
good idea and I agree 100%. My git skills are a bit rusty but I am
going to take that as an opportunity to learn how to submit a patch
like a real kernel dev.
Give me a couple of hours and I'll send a corrected patch set.
Greetings,
next prev parent reply other threads:[~2021-05-25 21:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[email protected]>
2021-05-25 8:21 ` [PATCH] io_uring: Add to traces the req pointer when available Pavel Begunkov
2021-05-25 8:33 ` Pavel Begunkov
2021-05-25 21:26 ` Olivier Langlois
2021-05-25 21:48 ` Olivier Langlois
2021-05-25 22:28 ` Jens Axboe
2021-05-26 8:28 ` Olivier Langlois
2021-05-25 21:29 ` Olivier Langlois [this message]
2021-05-26 12:38 ` Stefan Metzmacher
2021-05-26 16:18 ` Olivier Langlois
2021-05-26 17:19 ` Olivier Langlois
2021-05-29 12:18 ` Pavel Begunkov
2021-05-28 22:42 ` Steven Rostedt
2021-05-29 12:30 ` Pavel Begunkov
2021-05-29 12:34 ` Pavel Begunkov
2021-05-29 17:55 ` 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=35ec5774cc87f1edab72e351b9d2cb0b1457b1e9.camel@trillion01.com \
[email protected] \
[email protected] \
[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