From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
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: Re: linux-next: Signed-off-by missing for commit in the v4l-dvb-next tree
Date: Thu, 9 Feb 2023 09:26:17 +0100 [thread overview]
Message-ID: <a524d4df-ea30-7823-fb2e-9f5b9ab7644e@xs4all.nl> (raw)
In-Reply-To: <20230209075636.313e54e0@canb.auug.org.au>
On 08/02/2023 21:56, Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> fd24c6974a3a ("media: Revert "media: saa7146: deprecate hexium_gemini/orion, mxb and ttpci"")
> a4ff09f5a690 ("media: Revert "media: av7110: move to staging/media/deprecated/saa7146"")
>
> are missing a Signed-off-by from their author.
>
Fixed. Thank you for reporting this.
Regards,
Hans
next prev parent reply other threads:[~2023-02-09 8:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 20:56 linux-next: Signed-off-by missing for commit in the v4l-dvb-next tree Stephen Rothwell
2023-02-09 8:26 ` Hans Verkuil [this message]
-- 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
2022-12-06 20:56 Stephen Rothwell
2022-12-07 10:08 ` Hans Verkuil
2022-12-07 12:03 ` Stephen Rothwell
2022-11-15 20:38 Stephen Rothwell
2022-11-27 21:20 ` 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=a524d4df-ea30-7823-fb2e-9f5b9ab7644e@xs4all.nl \
--to=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).