From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Antonio Borneo <antonio.borneo@foss.st.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Orson Zhai <orsonzhai@gmail.com>,
Chunyan Zhang <zhang.lyra@gmail.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Wilken Gottwalt <wilken.gottwalt@posteo.net>,
Chen-Yu Tsai <wens@kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
linux-remoteproc@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev
Subject: Re: [PATCH v4 04/15] hwspinlock: add callback to fill private data of a hwspinlock
Date: Wed, 18 Mar 2026 11:31:12 +0100 [thread overview]
Message-ID: <abp-8GlLkoBAUJj8@ninjato> (raw)
In-Reply-To: <dd21653b7343e261ec9c88c622c5facbba69df95.camel@foss.st.com>
Hi Antonio,
> this API is described in Documentation/locking/hwspinlock.rst
> in chapter 'API for implementors'.
>
> Changing the API parameters should require updating the documentation too.
I totally agree. I missed that.
> Since this API is changed again in 10/15, it's probably fine to update the
> documentation only once in the last 15/15.
Well, the changes are little, so I will change the documentation
whenever the API itself gets modified.
Thanks for the heads up!
Wolfram
next prev parent reply other threads:[~2026-03-18 10:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 7:55 [PATCH v4 00/15] hwspinlock: move device alloc into core and refactor includes Wolfram Sang
2026-03-10 7:55 ` [PATCH v4 03/15] hwspinlock: add helpers to retrieve core data Wolfram Sang
2026-03-10 9:32 ` Chen-Yu Tsai
2026-03-10 7:55 ` [PATCH v4 04/15] hwspinlock: add callback to fill private data of a hwspinlock Wolfram Sang
2026-03-17 13:54 ` Antonio Borneo
2026-03-18 10:31 ` Wolfram Sang [this message]
2026-03-10 7:55 ` [PATCH v4 08/15] hwspinlock: stm32: use new callback to initialize hwspinlock priv Wolfram Sang
2026-03-10 7:55 ` [PATCH v4 09/15] hwspinlock: sun6i: " Wolfram Sang
2026-03-10 9:39 ` Chen-Yu Tsai
2026-03-10 10:03 ` Wolfram Sang
2026-03-10 10:22 ` Wilken Gottwalt
2026-03-10 7:55 ` [PATCH v4 10/15] hwspinlock: handle hwspinlock device allocation in the core Wolfram Sang
2026-03-10 7:55 ` [PATCH v4 11/15] hwspinlock: move entries from internal to public header Wolfram Sang
2026-03-10 7:55 ` [PATCH v4 14/15] hwspinlock: refactor provider.h from " Wolfram Sang
2026-03-10 7:55 ` [PATCH v4 15/15] hwspinlock/treewide: refactor consumer.h " Wolfram Sang
2026-03-11 9:24 ` Linus Walleij
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=abp-8GlLkoBAUJj8@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andersson@kernel.org \
--cc=antonio.borneo@foss.st.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=mcoquelin.stm32@gmail.com \
--cc=orsonzhai@gmail.com \
--cc=samuel@sholland.org \
--cc=wens@kernel.org \
--cc=wilken.gottwalt@posteo.net \
--cc=zhang.lyra@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