From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Sergey Shtylyov <s.shtylyov@omp.ru>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-renesas-soc@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@intel.com>,
linux-arm-kernel@lists.infradead.org,
Bjorn Andersson <andersson@kernel.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
linux-remoteproc@vger.kernel.org
Subject: Re: [RFC PATCH v2 02/13] hwspinlock: add callback to fill private data of a hwspinlock
Date: Mon, 16 Feb 2026 17:54:05 +0100 [thread overview]
Message-ID: <aZNLrRcMZXv4pdbN@shikoro> (raw)
In-Reply-To: <5416c451-43fc-4feb-b3be-6d6754720884@omp.ru>
Hi Sergey,
> > That I don't know. I just know that I did build-testing for the whole
> > series and the buildbots reported success. Need to look up why this was
> > not caught.
>
> Maybe it just built the kernel after applying the entire series? :-)
My scripts build after every patch. As said, I have to double check why
it did not fail here. I used to think buildbots work the same, but
probably not as I got another success report after this thread already
had started.
> Perhaps you should update the existing users to just pass NULL as
> init_data in this patch, and only then do the full-blown updates of
> the individual drivers?
That sounds like a good option to me, thanks!
Happy hacking,
Wolfram
next prev parent reply other threads:[~2026-02-16 16:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-15 22:54 [RFC v2 PATCH 00/13] hwspinlock: move device alloc into core and refactor includes Wolfram Sang
2026-02-15 22:54 ` [RFC PATCH v2 01/13] hwspinlock: add helpers to retrieve core data Wolfram Sang
2026-02-15 22:54 ` [RFC PATCH v2 02/13] hwspinlock: add callback to fill private data of a hwspinlock Wolfram Sang
2026-02-16 8:05 ` Sergey Shtylyov
2026-02-16 8:29 ` Wolfram Sang
2026-02-16 10:12 ` Geert Uytterhoeven
2026-02-16 10:53 ` Wolfram Sang
2026-02-16 16:12 ` Sergey Shtylyov
2026-02-16 16:54 ` Wolfram Sang [this message]
2026-02-15 22:54 ` [RFC PATCH v2 03/13] hwspinlock: omap: use new callback to initialize hwspinlock priv Wolfram Sang
2026-02-15 22:54 ` [RFC PATCH v2 04/13] hwspinlock: qcom: " Wolfram Sang
2026-02-15 22:54 ` [RFC PATCH v2 05/13] hwspinlock: sprd: " Wolfram Sang
2026-02-15 22:54 ` [RFC PATCH v2 06/13] hwspinlock: stm32: " Wolfram Sang
2026-02-15 22:54 ` [RFC PATCH v2 07/13] hwspinlock: sun6i: " Wolfram Sang
2026-02-15 22:54 ` [RFC PATCH v2 08/13] hwspinlock: handle hwspinlock device allocation in the core Wolfram Sang
2026-02-15 22:54 ` [RFC PATCH v2 09/13] hwspinlock: move entries from internal to public header Wolfram Sang
2026-02-15 22:54 ` [RFC PATCH v2 10/13] hwspinlock: remove internal header Wolfram Sang
2026-02-15 22:54 ` [RFC PATCH v2 11/13] hwspinlock: sort include and update copyright Wolfram Sang
2026-02-15 22:54 ` [RFC PATCH v2 12/13] hwspinlock: refactor provider.h from public header Wolfram Sang
2026-02-15 22:54 ` [RFC PATCH v2 13/13] hwspinlock: refactor consumer.h " Wolfram Sang
2026-02-16 7:37 ` Andy Shevchenko
2026-02-16 16:07 ` Mark Brown
2026-02-18 19:56 ` Jonathan Cameron
2026-02-16 7:40 ` [RFC v2 PATCH 00/13] hwspinlock: move device alloc into core and refactor includes Andy Shevchenko
2026-02-16 8:34 ` Wolfram Sang
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=aZNLrRcMZXv4pdbN@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=andersson@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=s.shtylyov@omp.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.