mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Cc: khilman@baylibre.com,
	AngeloGioacchino Del Regno 
	<angelogioacchino.delregno@collabora.com>,
	roger.lu@mediatek.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 0/2] soc: mediatek: Cleanups for MediaTek SVS driver
Date: Fri, 26 Aug 2022 17:27:58 +0200	[thread overview]
Message-ID: <4f1d3e02-0b40-cd29-5339-df1715bed84f@gmail.com> (raw)
In-Reply-To: <20220825184616.2118870-1-nfraprado@collabora.com>



On 25/08/2022 20:46, Nícolas F. R. A. Prado wrote:
> 
> This is a cleanup-only series for the mtk-svs driver, enhancing the
> usage of standard Linux macros for bitfields for better readability
> and register set/get safety, switches to devm_ functions variants
> where possible and other general cleanups, getting this driver in a
> better overall shape.

Both patches pushed, thanks!

> 
> v1: https://lore.kernel.org/all/20220726141653.177948-1-angelogioacchino.delregno@collabora.com
> 
> Changes in v2:
> - Rebased to not rely on mt8195 and mt8186 support, as they haven't been
>    merged yet
> 
> AngeloGioacchino Del Regno (2):
>    soc: mediatek: mtk-svs: Commonize t-calibration-data fuse array read
>    soc: mediatek: mtk-svs: Use bitfield access macros where possible
> 
>   drivers/soc/mediatek/mtk-svs.c | 260 ++++++++++++++++++++-------------
>   1 file changed, 160 insertions(+), 100 deletions(-)
> 

      parent reply	other threads:[~2022-08-26 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25 18:46 Nícolas F. R. A. Prado
2022-08-25 18:46 ` [PATCH v2 1/2] soc: mediatek: mtk-svs: Commonize t-calibration-data fuse array read Nícolas F. R. A. Prado
2022-08-25 18:46 ` [PATCH v2 2/2] soc: mediatek: mtk-svs: Use bitfield access macros where possible Nícolas F. R. A. Prado
2022-08-26 15:27 ` Matthias Brugger [this message]

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=4f1d3e02-0b40-cd29-5339-df1715bed84f@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=angelogioacchino.delregno@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=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

all inboxes | Powered by JetHome®