linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
	linux-mediatek@lists.infradead.org
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH v1 0/3] soc: mediatek: mtk-cmdq-helper: Various cleanups
Date: Thu, 3 Oct 2024 10:08:12 +0200	[thread overview]
Message-ID: <ae5eb5a8-d843-488a-8b68-9f6dd5d4603d@collabora.com> (raw)
In-Reply-To: <3e0c8b18-81ce-4c9b-886f-d7c50fdf4c3d@gmail.com>

Il 02/10/24 15:00, Matthias Brugger ha scritto:
> 
> 
> On 02/10/2024 11:08, AngeloGioacchino Del Regno wrote:
>> On Wed, 18 Sep 2024 12:06:17 +0200, AngeloGioacchino Del Regno wrote:
>>> This series performs various cleanups to the MediaTek CMDQ Helper lib,
>>> reducing code duplication and enhancing human readability.
>>>
>>> This also avoids double initialization struct cmdq_instruction as,
>>> in some cases, it was stack-initialized to zero and then overwritten
>>> completely anyway a bit later.
>>> I'd expect compilers to be somehow smart about that, but still, while
>>> at it ... why not :-)
>>>
>>> [...]
>>
>> Applied to v6.12-next/soc, thanks!
>>
>> [1/3] soc: mediatek: mtk-cmdq: Move mask build and append to function
>>        https://git.kernel.org/mediatek/c/2400e830
>> [2/3] soc: mediatek: mtk-cmdq: Mark very unlikely branches as such
>>        https://git.kernel.org/mediatek/c/21ab3dae
>> [3/3] soc: mediatek: mtk-cmdq: Move cmdq_instruction init to declaration
>>        https://git.kernel.org/mediatek/c/66705b89
>>
> 
> You probably oversaw the sparse warning email on 3/3?
> 
> As I oversaw that you already merged this.
> 

Yeah, I did. There's no problem anyway, as we can always replace the commits
without noise, I haven't pushed anything to -next :-)

I plan to do that (drop patch 2/3, delete `.mask = 0` on 3/3) soon, at max
next week anyway.

Cheers,
Angelo



  reply	other threads:[~2024-10-03  8:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18 10:06 [PATCH v1 0/3] soc: mediatek: mtk-cmdq-helper: Various cleanups AngeloGioacchino Del Regno
2024-09-18 10:06 ` [PATCH v1 1/3] soc: mediatek: mtk-cmdq: Move mask build and append to function AngeloGioacchino Del Regno
2024-10-02 12:33   ` Matthias Brugger
2024-09-18 10:06 ` [PATCH v1 2/3] soc: mediatek: mtk-cmdq: Mark very unlikely branches as such AngeloGioacchino Del Regno
2024-10-02 12:41   ` Matthias Brugger
2024-10-02 12:43     ` AngeloGioacchino Del Regno
2024-10-02 12:58       ` Matthias Brugger
2024-10-02 13:02         ` AngeloGioacchino Del Regno
2024-09-18 10:06 ` [PATCH v1 3/3] soc: mediatek: mtk-cmdq: Move cmdq_instruction init to declaration AngeloGioacchino Del Regno
2024-09-19 22:43   ` kernel test robot
2024-10-02 12:52   ` Matthias Brugger
2024-10-02  9:08 ` [PATCH v1 0/3] soc: mediatek: mtk-cmdq-helper: Various cleanups AngeloGioacchino Del Regno
2024-10-02 13:00   ` Matthias Brugger
2024-10-03  8:08     ` AngeloGioacchino Del Regno [this message]
2024-10-07 14:33       ` Matthias Brugger
2024-10-07 14:36         ` AngeloGioacchino Del Regno

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=ae5eb5a8-d843-488a-8b68-9f6dd5d4603d@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=kernel@collabora.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.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;
as well as URLs for NNTP newsgroup(s).