From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mauro Carvalho Chehab <mchehab@kernel•org>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Jason Chen <jasonx.z.chen@intel•com>,
Andy Yeh <andy.yeh@intel•com>,
Alan Chiang <alanx.chiang@intel•com>,
Sakari Ailus <sakari.ailus@linux•intel.com>,
Tomasz Figa <tfiga@chromium•org>,
Jacopo Mondi <jacopo@jmondi•org>, Rob Herring <robh@kernel•org>
Subject: linux-next: Signed-off-by missing for commits in the v4l-dvb tree
Date: Thu, 17 May 2018 07:37:02 +1000 [thread overview]
Message-ID: <20180517073702.5497e72e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
Hi Mauro,
Commit
af76c93aa36d ("media: cadence: csi2rx: Fix csi2rx_start error handling")
is missing a Signed-off-by from its committer.
Commits
c578c7710712 ("media: imx258: Add imx258 camera sensor driver")
3a8fdc1426c3 ("media: dw9807: Add dw9807 vcm driver")
2f9c1c88369f ("media: dt-bindings: Add bindings for Dongwoon DW9807 voice coil")
are missing a Signed-off-by from their author.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-05-16 21:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 21:37 Stephen Rothwell [this message]
2018-05-17 7:17 ` linux-next: Signed-off-by missing for commits in the v4l-dvb tree Sakari Ailus
2018-05-17 10:05 ` Mauro Carvalho Chehab
-- strict thread matches above, loose matches on Subject: below --
2021-09-30 10:59 Stephen Rothwell
2020-09-01 9:03 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
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=20180517073702.5497e72e@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=alanx.chiang@intel$(echo .)com \
--cc=andy.yeh@intel$(echo .)com \
--cc=jacopo@jmondi$(echo .)org \
--cc=jasonx.z.chen@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab@kernel$(echo .)org \
--cc=robh@kernel$(echo .)org \
--cc=sakari.ailus@linux$(echo .)intel.com \
--cc=tfiga@chromium$(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