devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Karl Li (李智嘉)" <Karl.Li@mediatek.com>,
	"AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>
Cc: "Chungying Lu (呂忠穎)" <Chungying.Lu@mediatek.com>,
	"Andy Teng (鄧如宏)" <Andy.Teng@mediatek.com>,
	Project_Global_Chrome_Upstream_Group
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"robh@kernel.org" <robh@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"jassisinghbrar@gmail.com" <jassisinghbrar@gmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"Chien-Chih Tseng (曾建智)" <Chien-Chih.Tseng@mediatek.com>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"wenst@chromium.org" <wenst@chromium.org>
Subject: Re: [PATCH 3/3] mailbox: mediatek: Add mtk-apu-mailbox driver
Date: Tue, 10 Dec 2024 09:45:04 +0100	[thread overview]
Message-ID: <b8c1c4d9-3234-4184-b57c-8cd5cb18f815@linaro.org> (raw)
In-Reply-To: <0d23ccf9-3420-45bf-aac7-5c1a075e031f@linaro.org>

On 10/12/2024 09:44, Krzysztof Kozlowski wrote:
> On 05/12/2024 08:32, Karl Li (李智嘉) wrote:
>> On Thu, 2024-12-05 at 07:05 +0000, Karl Li (李智嘉) wrote:
>>> Dead maintainers,
>> "Dear" maintainers. Really sorry for the typo...
>>>
>>> I hope you're doing well. Just a warm reminder that we're following
>>> up
>>> on these patch and really appreciate any feedback you might have.
>>>
> 
> You received like 6 or 7 reviews/replies for your patchset. What are you
> implying here if feedback was not enough?
> 
> Respond and implement the feedback instead ignoring it.
> 

Ah - and obvious static check warnings as well!

Please run standard kernel tools for static analysis, like coccinelle,
smatch and sparse, and fix reported warnings. Also please check for
warnings when building with W=1. Most of these commands (checks or W=1
build) can build specific targets, like some directory, to narrow the
scope to only your code. The code here looks like it needs a fix. Feel
free to get in touch if the warning is not clear.

Best regards,
Krzysztof


  reply	other threads:[~2024-12-10  8:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24  9:25 [PATCH 0/3] Add MediaTek APU Mailbox Support For MT8196 Karl.Li
2024-10-24  9:25 ` [PATCH 1/3] dt-bindings: mailbox: mediatek: Add apu-mailbox document Karl.Li
2024-10-24  9:42   ` Krzysztof Kozlowski
2024-10-24 11:08   ` AngeloGioacchino Del Regno
2024-10-24 13:45   ` Rob Herring (Arm)
2024-10-24  9:25 ` [PATCH 2/3] mailbox: add support for bottom half received data Karl.Li
2024-10-24 11:05   ` AngeloGioacchino Del Regno
2024-10-24  9:25 ` [PATCH 3/3] mailbox: mediatek: Add mtk-apu-mailbox driver Karl.Li
2024-10-24  9:45   ` Krzysztof Kozlowski
2024-10-24 11:04   ` AngeloGioacchino Del Regno
2024-10-28  6:16     ` Chen-Yu Tsai
2024-10-29  8:27       ` Karl Li (李智嘉)
2024-12-05  7:05         ` Karl Li (李智嘉)
2024-12-05  7:32           ` Karl Li (李智嘉)
2024-12-10  8:32             ` AngeloGioacchino Del Regno
2024-12-10  8:44             ` Krzysztof Kozlowski
2024-12-10  8:45               ` Krzysztof Kozlowski [this message]
2024-10-27  4:38   ` kernel test robot

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=b8c1c4d9-3234-4184-b57c-8cd5cb18f815@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=Andy.Teng@mediatek.com \
    --cc=Chien-Chih.Tseng@mediatek.com \
    --cc=Chungying.Lu@mediatek.com \
    --cc=Karl.Li@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh@kernel.org \
    --cc=wenst@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).