From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: alsa-devel@alsa-project.org
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Paul Menzel <paulepanter@users.sourceforge.net>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 1/5] ASoC: tlv320dac33: Update e-mail address
Date: Mon, 9 May 2011 13:44:03 +0300 [thread overview]
Message-ID: <201105091344.03914.peter.ujfalusi@ti.com> (raw)
In-Reply-To: <1304932469.3791.6.camel@mattotaupa>
Hi Paul,
On Monday 09 May 2011 12:14:29 Paul Menzel wrote:
> > * Platform header for Texas Instruments TLV320DAC33 codec driver
> > *
> > * Author: Peter Ujfalusi <peter.ujfalusi@nokia.com>
> >
> > + * Contact: Peter Ujfalusi <peter.ujfalusi@ti.com>
>
> the author email address would still be invalid, would not it? That the
> code was written when you worked for Nokia is still traceable by the
> history and the below copyright, is not it?
I tried to find guidelines for this situation, but found none, but I have
asked around, and one suggestion was to just change the Author email address
(as you also suggesting), the other is to keep the Author as it was, and add
the Contact address (as I did).
You are right, that from the log it is clear that the bulk of the work is
done, while I was at Nokia...
Mark: Should I resend the patches, and only change the Author mail address
(and not adding the Contact)?
Thanks,
Péter
next prev parent reply other threads:[~2011-05-09 10:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 8:52 [PATCH 0/5] ASoC: Update e-mail address Peter Ujfalusi
2011-05-09 8:52 ` [PATCH 1/5] ASoC: tlv320dac33: " Peter Ujfalusi
2011-05-09 9:14 ` Paul Menzel
2011-05-09 10:44 ` Peter Ujfalusi [this message]
2011-05-09 12:30 ` Mark Brown
2011-05-09 8:52 ` [PATCH 2/5] ASoC: tpa6130a2: " Peter Ujfalusi
2011-05-09 8:52 ` [PATCH 3/5] ASoC: omap-mcbsp: " Peter Ujfalusi
2011-05-09 8:52 ` [PATCH 4/5] ASoC: omap-pcm: " Peter Ujfalusi
2011-05-09 8:52 ` [PATCH 5/5] ASoC: RX51: " Peter Ujfalusi
2011-05-09 9:42 ` [PATCH 0/5] ASoC: " Mark Brown
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=201105091344.03914.peter.ujfalusi@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
--cc=paulepanter@users.sourceforge.net \
/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).