From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mauro Carvalho Chehab <mchehab@kernel•org>
Cc: Dillon Min <dillon.minfei@gmail•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: Fixes tags need some work in the v4l-dvb-next tree
Date: Tue, 16 Nov 2021 08:10:51 +1100 [thread overview]
Message-ID: <20211116081051.2066724f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
Hi all,
In commit
d9fbdedc56ea ("media: stm32-dma2d: fix compile-testing failed")
Fixes tag
Fixes: bff6e3e2f4c9 ("media: stm32-dma2d: STM32 DMA2D driver")
has these problem(s):
- Target SHA1 does not exist
Maybe you meant
Fixes: 002e8f0d5927 ("media: stm32-dma2d: STM32 DMA2D driver")
In commit
147907e93224 ("media: stm32-dma2d: fix compile errors when W=1")
Fixes tag
Fixes: bff6e3e2f4c9 ("media: stm32-dma2d: STM32 DMA2D driver")
has these problem(s):
- Target SHA1 does not exist
Maybe you meant
Fixes: 002e8f0d5927 ("media: stm32-dma2d: STM32 DMA2D driver")
In commit
22f2cac62dea ("media: atomisp-ov2680: properly set the vts value")
Fixes tag
Fixes: 62b984359b6f ("media: atomisp-ov2680: Fix ov2680_set_fmt() messing up high exposure settings")
has these problem(s):
- Target SHA1 does not exist
Maybe you meant
Fixes: 29400b5063db ("media: atomisp-ov2680: Fix ov2680_set_fmt() messing up high exposure settings")
In commit
d9916e7c87c9 ("media: atomisp-ov2680: initialize return var")
Fixes tag
Fixes: 6b5b60687ada ("media: atomisp-ov2680: Save/restore exposure and gain over sensor power-down")
has these problem(s):
- Target SHA1 does not exist
Maybe you meant
Fixes: 4ed2caf85337 ("media: atomisp-ov2680: Save/restore exposure and gain over sensor power-down")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2021-11-15 21:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211116081051.2066724f@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dillon.minfei@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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