From: Thomas Gleixner <tglx@linutronix.de>
To: Markus Elfring <Markus.Elfring@web.de>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Marc Zyngier <maz@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [v4] irqchip/renesas-rzg2l: Fix missing put_device
Date: Thu, 17 Oct 2024 00:00:30 +0200 [thread overview]
Message-ID: <87cyjzaetd.ffs@tglx> (raw)
In-Reply-To: <692cabd4-038b-403a-b21e-69a2b0492e57@web.de>
On Wed, Oct 16 2024 at 11:38, Markus Elfring wrote:
>> But this change fixes a bug and that's it.
>
> Maybe.
Maybe?
There is no maybe. You clearly failed to read and understand the
documentation I asked you to read and understand.
Either you are impersonating a badly implemented LLM or you are actually
living in the delusion that you can teach people who are actually doing
work based on your particular flavor of hubris.
Your answer to this mail will clearly tell me into which category you
fall into, but neither of them are in any way useful to the Linux kernel
community.
Whatever the answer is, I don't care because your input is completely
irrelevant. You have proven that over the years.
Thanks,
tglx
next prev parent reply other threads:[~2024-10-16 22:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 17:20 [PATCH v4] irqchip/renesas-rzg2l: Fix missing put_device Fabrizio Castro
2024-10-11 18:48 ` Markus Elfring
2024-10-15 21:52 ` Thomas Gleixner
2024-10-16 9:38 ` [v4] " Markus Elfring
2024-10-16 14:35 ` Thomas Gleixner
2024-10-16 22:00 ` Thomas Gleixner [this message]
2024-10-15 22:03 ` [tip: irq/urgent] " tip-bot2 for Fabrizio Castro
2024-10-17 12:21 ` [PATCH v4] " Lad, Prabhakar
2025-02-11 15:11 ` Geert Uytterhoeven
2025-02-11 15:49 ` Fabrizio Castro
2025-02-11 16:16 ` Geert Uytterhoeven
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=87cyjzaetd.ffs@tglx \
--to=tglx@linutronix.de \
--cc=Chris.Paterson2@renesas.com \
--cc=Markus.Elfring@web.de \
--cc=biju.das.jz@bp.renesas.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maz@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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