From: "Krzysztof Wilczy��ski" <kwilczynski@kernel.org>
To: Niklas Cassel <cassel@kernel.org>
Cc: Hans Zhang <Hans.Zhang@cixtech.com>,
kernel test robot <lkp@intel.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Wilfred Mallawa <wilfred.mallawa@wdc.com>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: 回复: [pci:slot-reset 1/1] drivers/pci/controller/dwc/pcie-dw-rockchip.c:721:58: error: use of undeclared identifier 'PCIE_CLIENT_GENERAL_CON'
Date: Fri, 16 May 2025 19:36:33 +0900 [thread overview]
Message-ID: <20250516103633.GA448167@rocinante> (raw)
In-Reply-To: <aCcGkN-9pN-jUwkS@ryzen>
Hello,
[...]
> Comparing the commit that landed on the branch, with Wilfred's patch on the
> mailing list, I did notice this diff:
[...]
> Reviewing the diff, the changes looks fine to me, but I strongly think
> that if the actual code is modified from the submission (rather than
> just fixing some minor grammar in the commit message), the (unwritten?)
> rule is that the person should add a:
>
> [person: describe modifications from the original submission]
Sorry about that. I did forgot to add this. Good catch.
That said, a single single line with a nudge or a reminder would suffice.
There is no need for a condescending tone and the lecturing and such.
You have been doing this for a while now, and if you continue doing this,
I will have no choice but to start to ignore submissions from you, I do not
have the time to deal with any forms of such passive-aggressive attitude.
Thank you!
Krzysztof
next prev parent reply other threads:[~2025-05-16 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 15:24 [pci:slot-reset 1/1] drivers/pci/controller/dwc/pcie-dw-rockchip.c:721:58: error: use of undeclared identifier 'PCIE_CLIENT_GENERAL_CON' kernel test robot
2025-05-15 15:54 ` 回复: " Hans Zhang
2025-05-15 15:54 ` Hans Zhang
2025-05-15 16:24 ` Krzysztof Wilczy��ski
2025-05-15 22:42 ` Wilfred Mallawa
2025-05-16 9:34 ` Niklas Cassel
2025-05-16 10:36 ` Krzysztof Wilczy��ski [this message]
2025-05-16 12:29 ` Niklas Cassel
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=20250516103633.GA448167@rocinante \
--to=kwilczynski@kernel.org \
--cc=Hans.Zhang@cixtech.com \
--cc=cassel@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=manivannan.sadhasivam@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wilfred.mallawa@wdc.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 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.