From: Archit Taneja <architt@codeaurora.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: David Airlie <airlied@linux.ie>,
Andrzej Hajda <a.hajda@samsung.com>,
Russell King <rmk+kernel@armlinux.org.uk>,
Mark Brown <broonie@kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jose Abreu <joabreu@synopsys.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH][resend] drm: dw-hdmi-i2s: add missing company name on Copyright
Date: Mon, 7 Aug 2017 09:29:22 +0530 [thread overview]
Message-ID: <81f62a86-ab2b-1379-c804-4245abc0f69a@codeaurora.org> (raw)
In-Reply-To: <87y3qwhwai.wl%kuninori.morimoto.gx@renesas.com>
On 08/07/2017 09:25 AM, Kuninori Morimoto wrote:
>
> Hi Archit
>
> Thank you for your feedback
>
>> On 08/07/2017 07:41 AM, Kuninori Morimoto wrote:
>>>
>>> From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>>>
>>> This driver's Copyright is under Renesas Solutions Corp
>>
>> Can we update the year to 2017 while we're at it?
>
> The original patch was created and applied on 2016
>
> 2761ba6c0925ca9c5b917a95f68135d9dce443fb
> ("drm: bridge: add DesignWare HDMI I2S audio support")
>
> And moved into new synopsys folder on 2017, I think.
We're allowed to update the copyright year as we continue to
make changes to a file. So, I think updating to 2017 should be
okay.
Archit
>
>
> Best regards
> ---
> Kuninori Morimoto
>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-08-07 3:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 2:11 [PATCH][resend] drm: dw-hdmi-i2s: add missing company name on Copyright Kuninori Morimoto
2017-08-07 3:34 ` Archit Taneja
2017-08-07 3:55 ` Kuninori Morimoto
2017-08-07 3:59 ` Archit Taneja [this message]
2017-08-07 4:03 ` Kuninori Morimoto
-- strict thread matches above, loose matches on Subject: below --
2017-07-24 1:20 Kuninori Morimoto
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=81f62a86-ab2b-1379-c804-4245abc0f69a@codeaurora.org \
--to=architt@codeaurora.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=joabreu@synopsys.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
/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