linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Tian Shu Qiu <tian.shu.qiu@intel.com>,
	Yong Zhi <yong.zhi@intel.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	"Cao,Bing Bu" <bingbu.cao@intel.com>
Subject: Re: linux-next: Signed-off-by missing for commit in the v4l-dvb-next tree
Date: Mon, 17 Dec 2018 18:39:17 -0200	[thread overview]
Message-ID: <20181217183909.3a06fbb4@coco.lan> (raw)
In-Reply-To: <20181216172339.486781e5@canb.auug.org.au>

Em Sun, 16 Dec 2018 17:23:39 +1100
Stephen Rothwell <sfr@canb.auug.org.au> escreveu:

> Hi Mauro,
> 
> Commit
> 
>   7ab9b77a9410 ("media: staging/intel-ipu3: Add dual pipe support")
> 
> is missing a Signed-off-by from its author.

The original author sent his SOB. I rebased the topic branch in order
to contain it.

Thanks for the warning!

Thanks,
Mauro

  reply	other threads:[~2018-12-17 20:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-16  6:23 linux-next: Signed-off-by missing for commit in the v4l-dvb-next tree Stephen Rothwell
2018-12-17 20:39 ` Mauro Carvalho Chehab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-07 21:01 Stephen Rothwell
2022-03-08  8:15 ` Hans Verkuil
2022-03-14 20:52 Stephen Rothwell
2022-11-15 20:38 Stephen Rothwell
2022-11-27 21:20 ` Stephen Rothwell
2022-12-06 20:56 Stephen Rothwell
2022-12-07 10:08 ` Hans Verkuil
2022-12-07 12:03   ` Stephen Rothwell
2023-02-08 20:56 Stephen Rothwell
2023-02-09  8:26 ` Hans Verkuil
2023-07-30 22:00 Stephen Rothwell
2023-08-14 23:11 Stephen Rothwell
2023-08-20 22:15 ` Stephen Rothwell
2023-10-08 21:26 Stephen Rothwell
2023-10-08 23:12 ` Mauro Carvalho Chehab
2024-07-03  6:33 Stephen Rothwell
2024-07-03  9:17 ` Hans Verkuil
2024-07-03 11:35   ` 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=20181217183909.3a06fbb4@coco.lan \
    --to=mchehab@kernel.org \
    --cc=bingbu.cao@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tian.shu.qiu@intel.com \
    --cc=yong.zhi@intel.com \
    /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).