From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Nikolay Kulikov <nikolayof23@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-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH v4 0/5] staging: media: atomisp: cleanup pci/hmm/ code
Date: Mon, 17 Aug 2026 10:36:51 +0300 [thread overview]
Message-ID: <aoK6E58VGAVRKuSZ@ashevche-desk.local> (raw)
In-Reply-To: <20260814-atomisp_remove_hmm-v4-0-c3c954a12b51@gmail.com>
On Fri, Aug 14, 2026 at 06:10:07PM +0300, Nikolay Kulikov wrote:
> This series removes unused functions and replaces obscure
> variable-checking macros with clear conditional statements.
> Nikolay Kulikov (5):
> staging: media: atomisp: remove unused functions from pci/hmm/
> staging: media: atomisp: inline macros for checking the bo/bodev pointer
> staging: media: atomisp: inline the check_bo_status_*() macros
> staging: media: atomisp: inline the var_equal_return*() macros
> staging: media: atomisp: remove hmm/hmm_common.h file
I don't know what the problem is, but in all four versions of this series
I have never get patch 5 in my mailbox (yes, I can retrieve it from
lore.kernel.org, but the thing is that either corporate spam-filter or
something else gates the message to me).
Overall, LGTM, thanks for pursuing this!
Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
for the entire series.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-08-17 7:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 15:10 [PATCH v4 0/5] staging: media: atomisp: cleanup pci/hmm/ code Nikolay Kulikov
2026-08-14 15:10 ` [PATCH v4 1/5] staging: media: atomisp: remove unused functions from pci/hmm/ Nikolay Kulikov
2026-08-14 15:10 ` [PATCH v4 2/5] staging: media: atomisp: inline macros for checking the bo/bodev pointer Nikolay Kulikov
2026-08-14 15:10 ` [PATCH v4 3/5] staging: media: atomisp: inline the check_bo_status_*() macros Nikolay Kulikov
2026-08-14 15:10 ` [PATCH v4 4/5] staging: media: atomisp: inline the var_equal_return*() macros Nikolay Kulikov
2026-08-14 15:10 ` [PATCH v4 5/5] staging: media: atomisp: remove hmm/hmm_common.h file Nikolay Kulikov
2026-08-17 7:36 ` 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=aoK6E58VGAVRKuSZ@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=nikolayof23@gmail.com \
--cc=sakari.ailus@linux.intel.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