From: Al Viro <viro@zeniv.linux.org.uk>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Conor Dooley <conor@kernel.org>,
linux-fsi@lists.ozlabs.org, linux-aspeed@lists.ozlabs.org,
devicetree@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-spi@vger.kernel.org, kernel-janitors@vger.kernel.org,
Eddie James <eajames@linux.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Andi Shyti <andi.shyti@kernel.org>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Lakshmi Yadlapati <lakshmiy@us.ibm.com>,
Mark Brown <broonie@kernel.org>,
Ninad Palsule <ninad@linux.ibm.com>,
Rob Herring <robh@kernel.org>
Subject: Re: [v6 17/20] ARM: dts: aspeed: Add IBM Huygens BMC system
Date: Thu, 23 May 2024 21:33:39 +0100 [thread overview]
Message-ID: <20240523203339.GS2118490@ZenIV> (raw)
In-Reply-To: <d6289d1c-deae-49a3-9fc9-98a2f2e57802@web.de>
On Thu, May 23, 2024 at 09:46:48PM +0200, Markus Elfring wrote:
> >> Would you like to mention in the changelog that a hardware description
> >> should be extended anyhow?
> >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9#n94
> >
> > You are talking absolute crap here. Stop harassing contributors with
> > your inane comments.
>
> Why do you interpret my patch review contributions in this direction
> when the official Linux development documentation provides special advice
> on affected wording details?
Your "contributions" are garbage in general, and this thread is not an exception.
More specifically, you are picking an advice that is inapplicable, transforming
it into a question and "contributing" the result.
And your entire modus operandi fits that pattern - you spew random garbage and
expect the contributors to spend their time and efforts on checking if your
(contents-free) "advice" happens to make any sense.
That. Is. Worthless.
According to people who'd met you in person you *are* a member of our species,
and I can't exclude the possibility that in some other environments you might
be capable of sentience. Unfortunately, the kernel development is clearly
not among those.
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@zeniv.linux.org.uk>
To: linux-aspeed@lists.ozlabs.org
Subject: [v6 17/20] ARM: dts: aspeed: Add IBM Huygens BMC system
Date: Thu, 23 May 2024 21:33:39 +0100 [thread overview]
Message-ID: <20240523203339.GS2118490@ZenIV> (raw)
In-Reply-To: <d6289d1c-deae-49a3-9fc9-98a2f2e57802@web.de>
On Thu, May 23, 2024 at 09:46:48PM +0200, Markus Elfring wrote:
> >> Would you like to mention in the changelog that a hardware description
> >> should be extended anyhow?
> >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9#n94
> >
> > You are talking absolute crap here. Stop harassing contributors with
> > your inane comments.
>
> Why do you interpret my patch review contributions in this direction
> when the official Linux development documentation provides special advice
> on affected wording details?
Your "contributions" are garbage in general, and this thread is not an exception.
More specifically, you are picking an advice that is inapplicable, transforming
it into a question and "contributing" the result.
And your entire modus operandi fits that pattern - you spew random garbage and
expect the contributors to spend their time and efforts on checking if your
(contents-free) "advice" happens to make any sense.
That. Is. Worthless.
According to people who'd met you in person you *are* a member of our species,
and I can't exclude the possibility that in some other environments you might
be capable of sentience. Unfortunately, the kernel development is clearly
not among those.
next prev parent reply other threads:[~2024-05-23 20:33 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 19:25 [PATCH v6 00/20] ARM: dts: aspeed: Add IBM P11 BMC systems Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-22 19:25 ` [PATCH v6 01/20] spi: dt-bindings: Document the IBM FSI-attached SPI controller Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-22 19:25 ` [PATCH v6 02/20] dt-bindings: fsi: fsi2spi: Document SPI controller child nodes Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-22 19:25 ` [PATCH v6 03/20] dt-bindings: fsi: Document the IBM SCOM engine Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-23 9:28 ` Markus Elfring
2024-05-23 9:28 ` Markus Elfring
2024-05-23 9:43 ` Conor Dooley
2024-05-23 9:45 ` Conor Dooley
2024-05-23 11:05 ` [v6 " Markus Elfring
2024-05-23 11:05 ` Markus Elfring
2024-05-22 19:25 ` [PATCH v6 04/20] dt-bindings: fsi: p9-occ: Convert to json-schema Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-23 15:37 ` Markus Elfring
2024-05-23 15:37 ` Markus Elfring
2024-05-22 19:25 ` [PATCH v6 05/20] dt-bindings: fsi: Document the IBM SBEFIFO engine Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-23 15:55 ` Markus Elfring
2024-05-23 15:55 ` Markus Elfring
2024-05-22 19:25 ` [PATCH v6 06/20] dt-bindings: fsi: Document the FSI controller common properties Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-23 6:57 ` Krzysztof Kozlowski
2024-05-23 6:57 ` Krzysztof Kozlowski
2024-05-22 19:25 ` [PATCH v6 07/20] dt-bindings: fsi: ibm,i2cr-fsi-master: Reference common FSI controller Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-22 19:25 ` [PATCH v6 08/20] dt-bindings: fsi: ast2600-fsi-master: Convert to json-schema Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-22 19:25 ` [PATCH v6 09/20] dt-bindings: fsi: Document the AST2700 FSI controller Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-22 19:25 ` [PATCH v6 10/20] dt-bindings: fsi: Document the FSI Hub Controller Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-28 14:58 ` Ninad Palsule
2024-05-22 19:25 ` [PATCH v6 11/20] dt-bindings: i2c: i2c-fsi: Convert to json-schema Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-23 6:59 ` Krzysztof Kozlowski
2024-05-23 6:59 ` Krzysztof Kozlowski
2024-05-28 14:52 ` Ninad Palsule
2024-05-28 14:52 ` Ninad Palsule
2024-05-22 19:25 ` [PATCH v6 12/20] dt-bindings: arm: aspeed: add IBM P11 BMC boards Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-28 14:24 ` Ninad Palsule
2024-05-28 14:24 ` Ninad Palsule
2024-05-22 19:25 ` [PATCH v6 13/20] ARM: dts: aspeed: Add IBM P11 FSI devices Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-28 14:22 ` Ninad Palsule
2024-05-22 19:25 ` [PATCH v6 14/20] ARM: dts: aspeed: Add IBM P11 Blueridge BMC system Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-24 22:47 ` Ninad Palsule
2024-05-28 14:50 ` Eddie James
2024-05-28 14:50 ` Eddie James
2024-05-22 19:25 ` [PATCH v6 15/20] ARM: dts: aspeed: Add IBM P11 Blueridge 4U " Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-24 22:27 ` Ninad Palsule
2024-05-24 22:27 ` Ninad Palsule
2024-05-22 19:25 ` [PATCH v6 16/20] ARM: dts: aspeed: Add IBM P11 Fuji " Eddie James
2024-05-22 19:26 ` Eddie James
2024-05-28 14:08 ` Ninad Palsule
2024-05-28 14:47 ` Eddie James
2024-05-28 14:47 ` Eddie James
2024-05-22 19:25 ` [PATCH v6 17/20] ARM: dts: aspeed: Add IBM Huygens " Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-23 12:48 ` kernel test robot
2024-05-23 12:48 ` kernel test robot
2024-05-23 19:07 ` Eddie James
2024-05-23 19:07 ` Eddie James
2024-05-23 18:45 ` Markus Elfring
2024-05-23 18:45 ` Markus Elfring
2024-05-23 19:00 ` Eddie James
2024-05-23 19:00 ` Eddie James
2024-05-23 19:30 ` [v6 " Markus Elfring
2024-05-23 19:30 ` Markus Elfring
2024-05-23 19:33 ` Conor Dooley
2024-05-23 19:33 ` Conor Dooley
2024-05-23 19:46 ` Markus Elfring
2024-05-23 19:46 ` Markus Elfring
2024-05-23 20:33 ` Al Viro [this message]
2024-05-23 20:33 ` Al Viro
2024-05-24 6:38 ` Markus Elfring
2024-05-24 6:38 ` Markus Elfring
2024-05-23 20:24 ` [PATCH v6 " Krzysztof Kozlowski
2024-05-23 20:24 ` Krzysztof Kozlowski
2024-05-23 20:33 ` [v6 " Markus Elfring
2024-05-23 20:33 ` Markus Elfring
2024-05-23 21:38 ` [PATCH v6 " Ninad Palsule
2024-05-23 21:38 ` Ninad Palsule
2024-05-22 19:25 ` [PATCH v6 18/20] fsi: occ: Get device number from FSI minor number API Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-23 21:36 ` Ninad Palsule
2024-05-23 21:36 ` Ninad Palsule
2024-05-22 19:25 ` [PATCH v6 19/20] fsi: occ: Find next available child rather than node name match Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-22 19:25 ` [PATCH v6 20/20] fsi: scom: Update compatible string to match documentation Eddie James
2024-05-22 19:25 ` Eddie James
2024-05-23 21:29 ` Ninad Palsule
2024-05-23 21:29 ` Ninad Palsule
2024-05-23 21:31 ` [PATCH v6 19/20] fsi: occ: Find next available child rather than node name match Ninad Palsule
2024-05-23 21:31 ` Ninad Palsule
2024-06-05 15:47 ` [PATCH v6 00/20] ARM: dts: aspeed: Add IBM P11 BMC systems Eddie James
2024-06-05 15:47 ` Eddie James
2024-06-06 1:31 ` Andrew Jeffery
2024-06-06 1:31 ` Andrew Jeffery
2024-07-08 13:47 ` Rob Herring
2024-07-08 13:47 ` Rob Herring
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=20240523203339.GS2118490@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=Markus.Elfring@web.de \
--cc=andi.shyti@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lakshmiy@us.ibm.com \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-fsi@lists.ozlabs.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=ninad@linux.ibm.com \
--cc=robh@kernel.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.