From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: "Rareș-Mihai Vladu" <vladurares@gmail.com>
Cc: Hans de Goede <hansg@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Andy Shevchenko <andy@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] media: atomisp: remove the circbuf library
Date: Tue, 27 Oct 2026 19:39:00 +0200 [thread overview]
Message-ID: <auDhtEFGht8PQnET@ashevche-desk.local> (raw)
In-Reply-To: <20261027120341.2305533-1-vladurares@gmail.com>
On Tue, Oct 27, 2026 at 12:03:35PM +0000, Rareș-Mihai Vladu wrote:
> Thanks to Andy for suggesting, in review of my earlier typedef
> patch [1], that I look at converting the custom circbuf code to
> circ_buf or kfifo, and for reviewing the previous versions.
>
> While looking into it, I found that the circbuf API is only used by
> the local queue path, and ia_css_queue_local_init() has no callers,
> so as far as I can tell that path is unused. The remote queues only
> need the descriptor and element layout shared with the SP firmware
> and a few small helpers.
>
> So this series first moves the remote queue handling into helpers,
> then removes the unused local path together with the queue type that
> no longer seems to serve a purpose, moves the few remaining pieces
> into ia_css_queue_comm.h and drops base/circbuf/. I may well be
> missing something, so please let me know if a different approach
> would be better and I will rework it.
>
> checkpatch warns about new typedefs in patch 4 and about MAINTAINERS
> in patch 5. The typedefs are only moved from ia_css_circbuf_comm.h,
> which patch 5 deletes, and MAINTAINERS has no entries for the removed
> files.
Almost there! The few minor amendments to the patch 2 and I think we
good to go, I believe next version will be final for this part of job.
> Compile-tested only.
>
> This supersedes the typedef patch [1].
And thanks for doing this! This is the real cleanup series from people who
want to learn while doing something against staging. I will point others
in the future to this success story.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-10-27 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 12:03 Rareș-Mihai Vladu
2026-10-27 12:03 ` [PATCH v3 1/5] media: atomisp: sh_css_mipi: include assert_support.h directly Rareș-Mihai Vladu
2026-10-27 12:03 ` [PATCH v3 2/5] media: atomisp: queue: move remote queue handling into helpers Rareș-Mihai Vladu
2026-10-27 17:26 ` Andy Shevchenko
2026-10-27 12:03 ` [PATCH v3 3/5] media: atomisp: queue: remove unused local queue support Rareș-Mihai Vladu
2026-10-27 17:27 ` Andy Shevchenko
2026-10-27 12:03 ` [PATCH v3 4/5] media: atomisp: queue: move circbuf types and helpers to queue_comm.h Rareș-Mihai Vladu
2026-10-27 17:34 ` Andy Shevchenko
2026-10-27 12:03 ` [PATCH v3 5/5] media: atomisp: remove unused circbuf library Rareș-Mihai Vladu
2026-10-27 17:39 ` Andy Shevchenko [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=auDhtEFGht8PQnET@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=vladurares@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
all inboxes | Powered by JetHome®