From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the v4l-dvb-fixes tree
Date: Thu, 15 Dec 2022 07:29:40 +1100 [thread overview]
Message-ID: <20221215072940.0c3538cf@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
Hi all,
Commits
542d3c03fd89 ("media: sun6i-isp: params: Unregister pending buffer on cleanup")
94c34359c887 ("media: sun6i-isp: params: Fix incorrect indentation")
7266eb7c5a52 ("media: sun6i-isp: capture: Fix uninitialized variable use")
44723b8c4692 ("media: sun6i-isp: proc: Declare subdev ops as static")
f72af7709478 ("media: sun6i-isp: proc: Error out on invalid port to fix warning")
504307f2b3ae ("media: sun6i-isp: proc: Fix return code handling in stream off path")
761ebebabd09 ("media: sun8i-a83t-mipi-csi2: Clarify return code handling in stream off path")
52109d91d2f9 ("media: sun6i-mipi-csi2: Clarify return code handling in stream off path")
f2c174e5018e ("media: sun6i-csi: capture: Remove useless ret initialization")
7fabed7ae618 ("media: sun6i-csi: bridge: Error out on invalid port to fix warning")
are missing a Signed-off-by from their committers.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-12-14 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 20:29 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-14 21:21 linux-next: Signed-off-by missing for commit in the v4l-dvb-fixes tree Stephen Rothwell
2023-09-14 21:35 ` Hans Verkuil
2023-05-08 20:34 Stephen Rothwell
2022-04-05 22:27 Stephen Rothwell
2020-01-08 20:26 Stephen Rothwell
2018-09-11 19:29 Stephen Rothwell
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=20221215072940.0c3538cf@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).