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 commits in the v4l-dvb tree
Date: Thu, 30 Sep 2021 20:59:07 +1000 [thread overview]
Message-ID: <20210930205907.6ddffc2d@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
Hi all,
Commits
a466530b3a1e ("watchdog/sb_watchdog: fix compilation problem due to COMPILE_TEST")
135291f36d22 ("vboxfs: fix broken legacy mount signature checking")
601e6baaa21c ("HID: amd_sfh: Fix potential NULL pointer dereference")
38245d0340ea ("HID: u2fzero: ignore incomplete packets without data")
ef1135704651 ("HID: amd_sfh: Fix potential NULL pointer dereference")
94f9c3567eba ("HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs")
125aaf6ec2fa ("HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS")
689e453a9b9c ("HID: betop: fix slab-out-of-bounds Write in betop_probe")
are missing a Signed-off-by from their committer.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-09-30 10:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 10:59 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-01 9:03 linux-next: Signed-off-by missing for commits in the v4l-dvb tree Stephen Rothwell
2020-09-01 10:05 ` Julia Lawall
2020-09-01 10:52 ` Mauro Carvalho Chehab
2020-09-01 12:10 ` Mauro Carvalho Chehab
2019-05-23 14:05 Stephen Rothwell
2019-05-23 14:10 ` Sakari Ailus
2019-05-23 14:20 ` Mauro Carvalho Chehab
2018-05-16 21:37 Stephen Rothwell
2018-05-17 7:17 ` Sakari Ailus
2018-05-17 10:05 ` Mauro Carvalho Chehab
2017-10-31 11:42 Stephen Rothwell
2017-09-25 23:09 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=20210930205907.6ddffc2d@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).