Linux kernel staging patches
 help / color / mirror / Atom feed
From: Nikolay Kulikov <nikolayof23@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Hans de Goede <hansg@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Andy Shevchenko <andy@kernel.org>,
	linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] staging: media: atomisp: cleanup pci/hmm/ code
Date: Thu, 13 Aug 2026 20:23:32 +0300	[thread overview]
Message-ID: <an39lHmSRfuEzU4b@archlinux> (raw)
In-Reply-To: <an2KlPmaXYxyVMEX@ashevche-desk.local>

On Thu, Aug 13, 2026 at 12:12:52PM +0300, Andy Shevchenko wrote:
> On Thu, Aug 13, 2026 at 12:11:04PM +0300, Andy Shevchenko wrote:
> > On Wed, Aug 12, 2026 at 11:51:33PM +0300, Nikolay Kulikov wrote:
> > > This series removes unused functions and replaces obscure
> > > variable-checking macros with clear conditional statements.
> > 
> > I believe I gave tags to some patches in v2. I don't see either.
> > What's going on?
> 
> For _this_ time, please reply yourself to the patches I already tagged with my
> Rb tags placed on a dedicated line.
> 
> > > Changes in v3:
> > > 	- Split the last patch into two (inlining macros and removing
> > > 	  the file).
> > > 	- Replace variable initialization with assignment, followed
> > > 	  immediately by a check.
> > > Changes in v2:
> > > 	- Squashed the function removals in pci/hmm/hmm.c and
> > > 	  pci/hmm/hmm_bo.c into a single commit.
> > > 	- Add commits to cleanup macros from include/hmm/hmm_common.h,
> > > 	  as suggested by Andy Shevchenko.
> > 
> > Also two process hints:
> > - add --base when prepare patches
> > - add links (URLs to lore.kernel.org) for the previous versions.
> 
> Same here, just reply to your cover letter with these URLs, and for this time
> just refer what the base was in a free form.

Sorry, I think I should have used b4 from the start.
I will send the new version with all the fixes.


Thanks,
Nikolay

      reply	other threads:[~2026-08-13 17:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12 20:51 [PATCH v3 0/5] staging: media: atomisp: cleanup pci/hmm/ code Nikolay Kulikov
2026-08-12 20:51 ` [PATCH v3 1/5] staging: media: atomisp: remove unused functions from pci/hmm/ Nikolay Kulikov
2026-08-12 20:51 ` [PATCH v3 2/5] staging: media: atomisp: inline macros for checking the bo/bodev pointer Nikolay Kulikov
2026-08-12 20:51 ` [PATCH v3 3/5] staging: media: atomisp: inline the check_bo_status_*() macros Nikolay Kulikov
2026-08-12 20:51 ` [PATCH v3 4/5] staging: media: atomisp: inline the var_equal_return*() macros Nikolay Kulikov
2026-08-12 20:51 ` [PATCH v3 5/5] staging: media: atomisp: remove hmm/hmm_common.h file Nikolay Kulikov
2026-08-13  9:10 ` [PATCH v3 0/5] staging: media: atomisp: cleanup pci/hmm/ code Andy Shevchenko
2026-08-13  9:12   ` Andy Shevchenko
2026-08-13 17:23     ` Nikolay Kulikov [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=an39lHmSRfuEzU4b@archlinux \
    --to=nikolayof23@gmail.com \
    --cc=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 \
    /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