From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Helen Koike <helen.koike@collabora.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
jgebben@codeaurora.org,
Helen Fornazier <helen.fornazier@gmail.com>
Subject: Re: [PATCH v6] [media] vimc: Virtual Media Controller core, capture and sensor
Date: Wed, 25 Jan 2017 13:31:10 -0200 [thread overview]
Message-ID: <20170125133110.5b8ea573@vento.lan> (raw)
In-Reply-To: <20170125130345.GD7139@valkosipuli.retiisi.org.uk>
I won't be doing a review on it yet... I'll try to do it on the next
version. Just a quick notice:
Em Wed, 25 Jan 2017 15:03:46 +0200
Sakari Ailus <sakari.ailus@iki.fi> escreveu:
> > + * Copyright (C) 2016 Helen Koike F. <helen.fornazier@gmail.com>
>
> 2017 might be used now.
Please keep 2016 as the year you did the initial development. It
makes sense to change it to:
2016-2017
In order to reflect that you're also doing some work on it this year,
but preserving the initial date is important, IMHO.
--
Thanks,
Mauro
next prev parent reply other threads:[~2017-01-25 15:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 15:02 [PATCH v4] [media] vimc: Virtual Media Controller core, capture and sensor Helen Koike
2016-06-12 1:59 ` kbuild test robot
2016-06-12 2:11 ` kbuild test robot
2016-07-01 12:39 ` Hans Verkuil
2016-08-17 22:08 ` Helen Koike
2016-08-17 22:09 ` [PATCH v5] " Helen Koike
2016-08-22 10:57 ` Hans Verkuil
2016-09-04 20:02 ` [PATCH v6] " Helen Koike
2016-09-06 7:33 ` Hans Verkuil
2016-09-12 12:53 ` [PATCH] [media] MAINTAINERS: add vimc entry Helen Koike
2017-01-10 19:54 ` [PATCH v6] [media] vimc: Virtual Media Controller core, capture and sensor Laurent Pinchart
2017-01-11 1:30 ` Helen Koike
2017-03-10 13:08 ` Hans Verkuil
2017-03-10 13:42 ` Helen Koike
2017-03-25 17:11 ` [PATCH v7] " Helen Koike
2017-03-25 23:04 ` Helen Koike
2017-03-26 13:31 ` Sakari Ailus
2017-03-27 15:19 ` Helen Koike
2017-03-27 18:09 ` Mauro Carvalho Chehab
2017-03-28 10:00 ` Hans Verkuil
2017-03-28 11:38 ` Mauro Carvalho Chehab
2017-03-28 20:37 ` Sakari Ailus
2017-03-29 7:49 ` Hans Verkuil
2017-03-29 8:46 ` Sakari Ailus
[not found] ` <CAKQmDh9QoW7qnai=i68HBBbkLBa+Ni5K7WKeYDLONjYeyhHH0A@mail.gmail.com>
2017-03-29 8:02 ` Hans Verkuil
2017-03-28 14:23 ` Sakari Ailus
2017-03-28 15:25 ` Mauro Carvalho Chehab
2017-03-28 20:39 ` Sakari Ailus
2017-03-29 7:39 ` Hans Verkuil
2017-03-27 9:00 ` Hans Verkuil
2017-03-27 13:33 ` [PATCH v8] " Helen Koike
2017-04-03 22:16 ` [PATCH v9] " Helen Koike
2017-04-06 14:29 ` Helen Koike
2017-04-07 9:54 ` Hans Verkuil
2017-04-07 17:55 ` [PATCH v10] " Helen Koike
2017-01-25 13:03 ` [PATCH v6] " Sakari Ailus
2017-01-25 15:31 ` Mauro Carvalho Chehab [this message]
2017-03-24 22:11 ` Helen Koike
2017-03-26 13:25 ` Sakari Ailus
2016-09-04 20:05 ` [PATCH v5] " Helen Koike
2016-09-05 9:01 ` Hans Verkuil
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=20170125133110.5b8ea573@vento.lan \
--to=mchehab@osg.samsung.com \
--cc=helen.fornazier@gmail.com \
--cc=helen.koike@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=jgebben@codeaurora.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
/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).