public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
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>,
	Dafna Hirschfeld <dafna.hirschfeld@collabora•com>,
	Hans Verkuil <hverkuil-cisco@xs4all•nl>
Subject: linux-next: Signed-off-by missing for commit in the v4l-dvb tree
Date: Mon, 28 Sep 2020 07:50:47 +1000	[thread overview]
Message-ID: <20200928075047.4fa3a02e@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 177 bytes --]

Hi all,

Commit

  2f8c737ed2c1 ("media: MAINTAINERS: add documentation files for rkisp1")

is missing a Signed-off-by from its author.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2020-09-27 21:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-27 21:50 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-09-10  7:39 linux-next: Signed-off-by missing for commit in the v4l-dvb tree Stephen Rothwell
2025-09-08 10:26 Stephen Rothwell
2023-08-14 23:06 Stephen Rothwell
2023-08-14 23:00 Stephen Rothwell
2022-04-05 22:32 Stephen Rothwell
2022-04-05 22:32 ` Stephen Rothwell
2022-04-06  0:02   ` Mauro Carvalho Chehab
2020-05-20 11:54 Stephen Rothwell
2020-03-16  7:45 Stephen Rothwell
2018-09-11 19:34 Stephen Rothwell
2018-08-11  4:35 Stephen Rothwell
2018-06-05 21:48 Stephen Rothwell
2018-03-08 20:46 Stephen Rothwell
2018-03-06 20:38 Stephen Rothwell
2017-12-29 23:21 Stephen Rothwell
2017-12-10  8:01 Stephen Rothwell
2017-09-25 21:27 Stephen Rothwell
2017-08-09 23:19 Stephen Rothwell
2017-08-08 21:47 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=20200928075047.4fa3a02e@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=dafna.hirschfeld@collabora$(echo .)com \
    --cc=hverkuil-cisco@xs4all$(echo .)nl \
    --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