From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Lubomir Rintel <lkundrak@v3.sk>, Shawnx Tu <shawnx.tu@intel.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commits in the v4l-dvb tree
Date: Thu, 23 May 2019 11:20:51 -0300 [thread overview]
Message-ID: <20190523112051.20418ef4@coco.lan> (raw)
In-Reply-To: <20190523141004.cfbuymuykjew4tyr@kekkonen.localdomain>
Em Thu, 23 May 2019 17:10:05 +0300
Sakari Ailus <sakari.ailus@linux.intel.com> escreveu:
> Hi Stephen, Mauro,
>
> On Fri, May 24, 2019 at 12:05:00AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Commits
> >
> > eeabf6320e2f ("media: Revert "[media] marvell-ccic: reset ccic phy when stop streaming for stability"")
> > bbf83ed40252c ("media: ov8856: modify register to fix test pattern")
> >
> > are missing a Signed-off-by from their authors.
>
> Ouch.
>
> Mauro, what do you prefer, reset the tree or what?
I'll drop bbf83ed40252c and the marvel-ccic patches after eeabf6320e2f,
rebasing my tree.
>
> Shawn, Lubomir: please read "Developer's Certificate of Origin 1.1" in
> Documentation/process/submitting-patches.rst and then resend with
> appropriate SoB lines.
>
Thanks,
Mauro
next prev parent reply other threads:[~2019-05-23 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 14:05 linux-next: Signed-off-by missing for commits in the v4l-dvb tree Stephen Rothwell
2019-05-23 14:10 ` Sakari Ailus
2019-05-23 14:20 ` Mauro Carvalho Chehab [this message]
-- 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
2018-05-16 21:37 Stephen Rothwell
2018-05-17 7:17 ` Sakari Ailus
2018-05-17 10:05 ` 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=20190523112051.20418ef4@coco.lan \
--to=mchehab@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=sakari.ailus@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=shawnx.tu@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).