public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: bin.lan.cn@eng.windriver.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1] media: mediatek: vcodec: Handle invalid decoder vsi
Date: Fri,  6 Dec 2024 12:11:20 -0500	[thread overview]
Message-ID: <20241206101302-c38e0bd25a209067@stable.kernel.org> (raw)
In-Reply-To: <20241206012712.593884-1-bin.lan.cn@eng.windriver.com>

[ Sasha's backport helper bot ]

Hi,

The upstream commit SHA1 provided is correct: 59d438f8e02ca641c58d77e1feffa000ff809e9f

WARNING: Author mismatch between patch and upstream commit:
Backport author: bin.lan.cn@eng.windriver.com
Commit author: Irui Wang <irui.wang@mediatek.com>


Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 1c109f23b271)
6.1.y | Not found

Note: The patch differs from the upstream commit:
---
1:  59d438f8e02ca < -:  ------------- media: mediatek: vcodec: Handle invalid decoder vsi
-:  ------------- > 1:  b76bf4673f978 media: mediatek: vcodec: Handle invalid decoder vsi
---

Results of testing on various branches:

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

Build Errors:
Build error for stable/linux-6.1.y:
    drivers/media/platform/mediatek/vcodec/vdec_vpu_if.c: In function 'vpu_dec_init':
    drivers/media/platform/mediatek/vcodec/vdec_vpu_if.c:218:17: error: implicit declaration of function 'mtk_vdec_err'; did you mean 'mtk_vcodec_err'? [-Wimplicit-function-declaration]
      218 |                 mtk_vdec_err(vpu->ctx, "invalid vdec vsi, status=%d", err);
          |                 ^~~~~~~~~~~~
          |                 mtk_vcodec_err
    make[6]: *** [scripts/Makefile.build:250: drivers/media/platform/mediatek/vcodec/vdec_vpu_if.o] Error 1
    make[6]: Target 'drivers/media/platform/mediatek/vcodec/' not remade because of errors.
    make[5]: *** [scripts/Makefile.build:503: drivers/media/platform/mediatek/vcodec] Error 2
    make[5]: Target 'drivers/media/platform/mediatek/' not remade because of errors.
    make[4]: *** [scripts/Makefile.build:503: drivers/media/platform/mediatek] Error 2
    make[4]: Target 'drivers/media/platform/' not remade because of errors.
    make[3]: *** [scripts/Makefile.build:503: drivers/media/platform] Error 2
    make[3]: Target 'drivers/media/' not remade because of errors.
    make[2]: *** [scripts/Makefile.build:503: drivers/media] Error 2
    make[2]: Target 'drivers/' not remade because of errors.
    make[1]: *** [scripts/Makefile.build:503: drivers] Error 2
    make[1]: Target './' not remade because of errors.
    make: *** [Makefile:2009: .] Error 2
    make: Target '__all' not remade because of errors.

      reply	other threads:[~2024-12-06 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06  1:27 [PATCH 6.1] media: mediatek: vcodec: Handle invalid decoder vsi bin.lan.cn
2024-12-06 17:11 ` Sasha Levin [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=20241206101302-c38e0bd25a209067@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=bin.lan.cn@eng.windriver.com \
    --cc=stable@vger.kernel.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