public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>,
	Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.12.y] media: ipu6: use the IPU6 DMA mapping APIs to do mapping
Date: Mon,  9 Dec 2024 15:55:53 -0500	[thread overview]
Message-ID: <20241209140015-9d5855e4e01a460e@stable.kernel.org> (raw)
In-Reply-To: <20241209175416.59433-1-stanislaw.gruszka@linux.intel.com>

[ Sasha's backport helper bot ]

Hi,

The upstream commit SHA1 provided is correct: 1d4a000289979cc7f2887c8407b1bfe2a0918354

WARNING: Author mismatch between patch and upstream commit:
Backport author: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
Commit author: Bingbu Cao <bingbu.cao@intel.com>


Status in newer kernel trees:
6.12.y | Not found

Note: The patch differs from the upstream commit:
---
1:  1d4a000289979 ! 1:  b5698951cc16d media: ipu6: use the IPU6 DMA mapping APIs to do mapping
    @@ Metadata
      ## Commit message ##
         media: ipu6: use the IPU6 DMA mapping APIs to do mapping
     
    +    commit 1d4a000289979cc7f2887c8407b1bfe2a0918354 upstream.
    +
         dma_ops is removed from the IPU6 auxiliary device, ISYS driver
         should use the IPU6 DMA mapping APIs directly instead of depending
         on the device callbacks.
    @@ Commit message
         [Sakari Ailus: Rebased on recent videobuf2 wait changes.]
         Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
         Signed-off-by: Hans Verkuil <hverkuil@xs4all.nl>
    +    Signed-off-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
     
      ## drivers/media/pci/intel/ipu6/Kconfig ##
     @@ drivers/media/pci/intel/ipu6/Kconfig: config VIDEO_INTEL_IPU6
    @@ drivers/media/pci/intel/ipu6/ipu6-isys-queue.c: void ipu6_isys_queue_buf_ready(s
      static const struct vb2_ops ipu6_isys_queue_ops = {
     -	.queue_setup = queue_setup,
     +	.queue_setup = ipu6_isys_queue_setup,
    -+	.wait_prepare = vb2_ops_wait_prepare,
    -+	.wait_finish = vb2_ops_wait_finish,
    + 	.wait_prepare = vb2_ops_wait_prepare,
    + 	.wait_finish = vb2_ops_wait_finish,
     +	.buf_init = ipu6_isys_buf_init,
      	.buf_prepare = ipu6_isys_buf_prepare,
     +	.buf_cleanup = ipu6_isys_buf_cleanup,
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y       |  Success    |  Success   |

  reply	other threads:[~2024-12-09 20:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-09 17:54 [PATCH 6.12.y] media: ipu6: use the IPU6 DMA mapping APIs to do mapping Stanislaw Gruszka
2024-12-09 20:55 ` Sasha Levin [this message]
2024-12-11 14:01 ` Hans de Goede

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=20241209140015-9d5855e4e01a460e@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=stanislaw.gruszka@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