Linux Media Controller development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-media@vger.kernel.org
Cc: Ricardo Ribalda <ribalda@chromium.org>
Subject: Re: [v2,0/2] media: renesas: vsp1: Fix display pipeline regression
Date: Thu, 7 May 2026 02:11:34 +0300	[thread overview]
Message-ID: <20260506231134.GD1778786@killaraus.ideasonboard.com> (raw)
In-Reply-To: <69fbc7c8.9d0a0220.1bdb77.e857@mx.google.com>

On Wed, May 06, 2026 at 03:59:20PM -0700, Patchwork Integration wrote:
> Dear Laurent Pinchart:
> 
> Thanks for your patches! Unfortunately the Media CI robot detected some
> issues:
> 
> # Test media-patchstyle:./0001-Revert-media-renesas-vsp1-Initialize-format-on-all-p.patch media style
> ERROR: ./0001-Revert-media-renesas-vsp1-Initialize-format-on-all-p.patch: Missing committer Ricardo Ribalda <ribalda@chromium.org> Signed-off-by
> ERROR: Commit 133ac42af0a1b389e8b7b3dc7c1cc8c30ff162b6 found in the stable tree, but stable@vger.kernel.org not in Cc:
> 
> # Test media-patchstyle:./0002-Revert-media-renesas-vsp1-brx-Fix-format-propagation.patch media style
> ERROR: ./0002-Revert-media-renesas-vsp1-brx-Fix-format-propagation.patch: Missing committer Ricardo Ribalda <ribalda@chromium.org> Signed-off-by

I'm not going to add your SoB to my patches :-)

> ERROR: Commit 937f3e6b51f1cea079be9ba642665f2bf8bcc31f found in the stable tree, but stable@vger.kernel.org not in Cc:

I don't see these commits in any of the stable branches. Does the
message mean the mainline tree, not the stable tree ?

Given that this series should be merged in v7.1 as a regression fix, why
should it CC stable ?

> Please fix your series, and upload a new version. If you have a patchwork
> account, do not forget to mark the current series as Superseded.
> 
> For more details, check the full report at:
> https://linux-media.pages.freedesktop.org/-/users/patchwork/-/jobs/99198847/artifacts/report.htm .
> 
> 
> 
> Best regards, and Happy Hacking!
> Media CI robot on behalf of the linux-media community.
> 
> ---
> Check the latest rules for contributing your patches at:
> https://docs.kernel.org/driver-api/media/maintainer-entry-profile.html
> 
> If you believe that the CI is wrong, kindly open an issue at
> https://gitlab.freedesktop.org/linux-media/media-ci/-/issues or reply-all
> to this message.

-- 
Regards,

Laurent Pinchart

  parent reply	other threads:[~2026-05-06 23:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06 21:56 [PATCH v2 0/2] media: renesas: vsp1: Fix display pipeline regression Laurent Pinchart
2026-05-06 21:56 ` [PATCH v2 1/2] Revert "media: renesas: vsp1: Initialize format on all pads" Laurent Pinchart
2026-05-07 16:01   ` Lad, Prabhakar
2026-05-06 21:56 ` [PATCH v2 2/2] Revert "media: renesas: vsp1: brx: Fix format propagation" Laurent Pinchart
2026-05-07 16:02   ` Lad, Prabhakar
     [not found] ` <69fbc7c8.9d0a0220.1bdb77.e857@mx.google.com>
2026-05-06 23:11   ` Laurent Pinchart [this message]
2026-05-07  5:30     ` [v2,0/2] media: renesas: vsp1: Fix display pipeline regression Ricardo Ribalda
2026-05-07  8:18       ` Laurent Pinchart
2026-05-07  8:38         ` Ricardo Ribalda
2026-05-07  8:44           ` Laurent Pinchart

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=20260506231134.GD1778786@killaraus.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=ribalda@chromium.org \
    /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