From: Olivier Langlois <olivier@trillion01.com>
To: Jens Axboe <axboe@kernel.dk>, Steven Rostedt <rostedt@goodmis.org>
Cc: Pavel Begunkov <asml.silence@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] io_uring: minor clean up in trace events definition
Date: Wed, 16 Jun 2021 15:00:55 -0400 [thread overview]
Message-ID: <3f5447bf02453a034f4eb71f092dd1d1455ec7ad.camel@trillion01.com> (raw)
In-Reply-To: <2ba15b09-2228-9a2a-3ac3-c471dd3fc912@kernel.dk>
On Wed, 2021-06-16 at 06:49 -0600, Jens Axboe wrote:
>
> Indeed, that is what is causing the situation, and I do have them
> here.
> Olivier, you definitely want to fix your mail setup. It confuses both
> MUAs, but it also actively prevents using the regular tooling to pull
> these patches off lore for example.
>
Ok, I will... It seems that only my patch emails are having this issue.
I am pretty sure that I can find instances of non patch emails going
making it to the lists...
next prev parent reply other threads:[~2021-06-16 19:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <60be7e31.1c69fb81.a8bfb.2e54SMTPIN_ADDED_MISSING@mx.google.com>
2021-06-15 9:48 ` [PATCH v2 2/3] io_uring: minor clean up in trace events definition Pavel Begunkov
2021-06-15 21:50 ` Jens Axboe
2021-06-15 23:35 ` Steven Rostedt
2021-06-16 12:49 ` Jens Axboe
2021-06-16 19:00 ` Olivier Langlois [this message]
2021-06-16 19:02 ` Jens Axboe
2021-06-16 21:30 ` Olivier Langlois
2021-06-16 21:33 ` Jens Axboe
2021-06-20 19:15 ` Olivier Langlois
2021-06-20 20:13 ` Pavel Begunkov
2021-06-16 13:33 ` Olivier Langlois
2021-06-16 13:43 ` Steven Rostedt
2021-06-16 13:53 ` Pavel Begunkov
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=3f5447bf02453a034f4eb71f092dd1d1455ec7ad.camel@trillion01.com \
--to=olivier@trillion01.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.