From: Thomas Gleixner <tglx@kernel.org>
To: "Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
"André Almeida" <andrealmeid@igalia.com>
Cc: linux-kernel@vger.kernel.org, Carlos O'Donell <carlos@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Florian Weimer <fweimer@redhat.com>,
Rich Felker <dalias@aerifal.cx>,
Torvald Riegel <triegel@redhat.com>,
Darren Hart <dvhart@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Arnd Bergmann <arnd@arndb.de>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>
Subject: Re: [RFC PATCH] futex: Introduce __vdso_robust_futex_unlock
Date: Tue, 24 Mar 2026 22:35:18 +0100 [thread overview]
Message-ID: <87v7ekgbc9.ffs@tglx> (raw)
In-Reply-To: <1786e0b7-b57e-4b64-9ae8-9dcc5a5dfbe8@efficios.com>
Mathieu!
On Fri, Mar 20 2026 at 14:13, Mathieu Desnoyers wrote:
Thanks for bringing this up. I reflected on my behavior and, first of all, I
want to offer my sincere apologies.
Allow me to share my reflections – neither to defend or excuse my behavior
nor to deflect it back to you – but as a form of honest root cause analysis.
I realized that I underestimated how differently the usage of hyperbolic
exaggeration – beyond the point of absurdity – is perceived across
different cultures and individuals.
It is generally known that the German communication style can be very
direct. As a thought experiment, I tried to imagine how I would receive the
same reply if sent to me. My initial unspoken thought would have probably
been, “Point taken. You bastard.” then, my reaction would have been either
to go silent and do more research or, if it annoyed me enough, to dryly
serve it back with, “Were you referring to the training about
professionalism and multicultural awareness? Was it any good?”
But I acknowledge that communication styles, expectations and perception
are very different across cultures and individuals. So I'll try to avoid it
in the future.
Honestly, my response was a signal that my patience was exhausted and my
frustration had crossed a threshold. I have publicly admitted in the past
that I have difficulties with this. I'm working on this, but every now and
then, my filter fails and I end up being too stingingly direct for my own
good.
Where does this frustration originate from?
1) The respect for other people's time is deeply cultural and ingrained in
me.
It's highly valued when people show up for technical discussions with
the details 'paged in'. Unpreparedness can be perceived as disregarding
others’ time.
I'm caring deeply about my time, which is a finite precious resource
and I'm very sensitive and protective about it so that I'm able to
distribute and re-prioritize it between bugs, regressions, submissions
and my own work.
2) In German engineering culture 'solved' is a binary state which implies
that something is complete, tested and well-explained.
Claiming it to be solved while noting that it's incomplete and untested
is not only a logical contradiction, but it can be perceived as a
breach of professional integrity or as an act of ‘marketing’.
Seeking feedback on an idea or proof of concept is certainly welcome and
encouraged, provided it's clearly communicated that way – along with an
explanation of the analysis which led to the approach.
3) Methodological rigor is a key expectation of my engineering culture.
Due to that, I spend significant amounts of time and effort to provide
full technical analysis with detailed break downs. These write-ups are
useful for myself to self check my conclusions and work but also aimed
to make it easy for the recipient to follow my thought process. I also
take care of documenting the expectations for patch submissions in order
to make the process smooth and less time consuming for everyone
involved.
I become deeply frustrated when I perceive that these efforts aren't
valued, not met with reciprocal rigor, and/or when documentation or
feedback is ignored – especially when it comes from people I respect
and I know they are capable.
I respect you as a person and I respect your technical expertise. I
absolutely had no intention to belittle you or to undermine your expertise.
I offer you my sincere apology once again.
Thomas
next prev parent reply other threads:[~2026-03-24 21:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 18:54 [RFC PATCH] futex: Introduce __vdso_robust_futex_unlock Mathieu Desnoyers
2026-03-11 20:11 ` Mathieu Desnoyers
2026-03-12 8:49 ` Florian Weimer
2026-03-12 13:13 ` Mathieu Desnoyers
2026-03-12 14:12 ` Florian Weimer
2026-03-12 14:14 ` André Almeida
2026-03-12 16:09 ` Mathieu Desnoyers
2026-03-12 13:46 ` André Almeida
2026-03-12 14:04 ` Mathieu Desnoyers
2026-03-12 18:40 ` Mathieu Desnoyers
2026-03-12 18:58 ` André Almeida
2026-03-12 19:10 ` Thomas Gleixner
2026-03-12 19:16 ` Mathieu Desnoyers
2026-03-13 8:20 ` Florian Weimer
2026-03-12 20:19 ` Thomas Gleixner
2026-03-12 21:28 ` Mathieu Desnoyers
2026-03-12 22:23 ` Thomas Gleixner
2026-03-12 22:52 ` Mathieu Desnoyers
2026-03-13 12:12 ` Sebastian Andrzej Siewior
2026-03-13 12:17 ` Mathieu Desnoyers
2026-03-13 13:29 ` Sebastian Andrzej Siewior
2026-03-13 13:35 ` Mathieu Desnoyers
2026-03-16 17:12 ` Thomas Gleixner
2026-03-16 19:36 ` Mathieu Desnoyers
2026-03-16 20:27 ` Thomas Gleixner
2026-03-16 21:01 ` Mathieu Desnoyers
2026-03-16 22:19 ` Thomas Gleixner
2026-03-16 22:30 ` Mathieu Desnoyers
2026-03-16 23:29 ` Thomas Gleixner
2026-03-20 18:13 ` Mathieu Desnoyers
2026-03-24 21:35 ` Thomas Gleixner [this message]
2026-03-25 14:12 ` Mathieu Desnoyers
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=87v7ekgbc9.ffs@tglx \
--to=tglx@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=andrealmeid@igalia.com \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=carlos@redhat.com \
--cc=dalias@aerifal.cx \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=fweimer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=triegel@redhat.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