linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Stanimir Varbanov <stanimir.varbanov@linaro.org>,
	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-next tree
Date: Wed, 16 Nov 2022 07:38:48 +1100	[thread overview]
Message-ID: <20221116073848.46178032@canb.auug.org.au> (raw)

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

Hi all,

Commits

  0f6e8d8c94a8 ("venus: pm_helpers: Fix error check in vcodec_domains_get()")
  ee357294a85b ("MAINTAINERS: Add Vikash as VENUS video driver co-maintainer")

are missing a Signed-off-by from their committer.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2022-11-15 20:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 20:38 Stephen Rothwell [this message]
2022-11-27 21:20 ` linux-next: Signed-off-by missing for commit in the v4l-dvb-next tree Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2023-10-08 21:26 Stephen Rothwell
2023-10-08 23:12 ` Mauro Carvalho Chehab
2023-08-14 23:11 Stephen Rothwell
2023-08-20 22:15 ` Stephen Rothwell
2023-07-30 22:00 Stephen Rothwell
2023-02-08 20:56 Stephen Rothwell
2023-02-09  8:26 ` Hans Verkuil
2022-12-06 20:56 Stephen Rothwell
2022-12-07 10:08 ` Hans Verkuil
2022-12-07 12:03   ` Stephen Rothwell
2022-03-14 20:52 Stephen Rothwell
2022-03-07 21:01 Stephen Rothwell
2022-03-08  8:15 ` Hans Verkuil
2018-12-16  6:23 Stephen Rothwell
2018-12-17 20:39 ` Mauro Carvalho Chehab

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=20221116073848.46178032@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 \
    --cc=stanimir.varbanov@linaro.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).