From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>
Cc: roger.lu@mediatek.com, khilman@baylibre.com,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH 6/6] soc: mediatek: mtk-svs: Use bitfield access macros where possible
Date: Mon, 29 Aug 2022 11:36:52 +0200 [thread overview]
Message-ID: <37cdcc41-8cfc-443a-a6d7-94b992a0b6f5@collabora.com> (raw)
In-Reply-To: <20220825185059.xbh3gigksveg4h4u@notapiano>
Il 25/08/22 20:50, Nícolas F. R. A. Prado ha scritto:
> On Thu, Aug 25, 2022 at 03:29:33PM +0200, Matthias Brugger wrote:
>>
>>
>> On 26/07/2022 16:16, AngeloGioacchino Del Regno wrote:
>>> In order to enhance readability and safety during registers setup
>>> and value retrieval, redefine a few register related macros and
>>> convert all open-coded instances of bitfield setting/retrieval
>>> to use the FIELD_PREP() and FIELD_GET() macros.
>>> While at it, some macros were renamed to further enhance readability.
>>>
>>> This commit brings no functional changes.
>>>
>>> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>>
>> Does not apply, would you mind to resend together with 1/6? Thanks!
>
> Hi Matthias,
>
> Patches 1 and 6 rebased and sent [1].
>
> Thanks,
> Nícolas
>
> [1] https://lore.kernel.org/all/20220825184616.2118870-1-nfraprado@collabora.com
Uh, sorry for the previous noise - didn't notice this email.
Many thanks for timely rebasing the patches!
Cheers!
next prev parent reply other threads:[~2022-08-29 9:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 14:16 [PATCH 0/6] soc: mediatek: Cleanups for MediaTek SVS driver AngeloGioacchino Del Regno
2022-07-26 14:16 ` [PATCH 1/6] soc: mediatek: mtk-svs: Commonize t-calibration-data fuse array read AngeloGioacchino Del Regno
2022-08-25 13:27 ` Matthias Brugger
2022-07-26 14:16 ` [PATCH 2/6] soc: mediatek: mtk-svs: Switch to platform_get_irq() AngeloGioacchino Del Regno
2022-08-25 13:26 ` Matthias Brugger
2022-07-26 14:16 ` [PATCH 3/6] soc: mediatek: mtk-svs: Remove hardcoded irqflags AngeloGioacchino Del Regno
2022-08-25 13:28 ` Matthias Brugger
2022-07-26 14:16 ` [PATCH 4/6] soc: mediatek: mtk-svs: Drop of_match_ptr() for of_match_table AngeloGioacchino Del Regno
2022-08-25 13:28 ` Matthias Brugger
2022-07-26 14:16 ` [PATCH 5/6] soc: mediatek: mtk-svs: Use devm variant for dev_pm_opp_of_add_table() AngeloGioacchino Del Regno
2022-08-25 13:28 ` Matthias Brugger
2022-07-26 14:16 ` [PATCH 6/6] soc: mediatek: mtk-svs: Use bitfield access macros where possible AngeloGioacchino Del Regno
2022-08-25 13:29 ` Matthias Brugger
2022-08-25 18:50 ` Nícolas F. R. A. Prado
2022-08-29 9:36 ` AngeloGioacchino Del Regno [this message]
2022-08-29 9:33 ` AngeloGioacchino Del Regno
2022-08-29 11:02 ` Matthias Brugger
2022-07-26 14:22 ` [PATCH 0/6] soc: mediatek: Cleanups for MediaTek SVS driver 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=37cdcc41-8cfc-443a-a6d7-94b992a0b6f5@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=kernel@collabora.com \
--cc=khilman@baylibre.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 \
--cc=nfraprado@collabora.com \
--cc=roger.lu@mediatek.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