From: Mark Brown <broonie@kernel.org>
To: Oder Chiou <oder_chiou@realtek.com>
Cc: Michele Curti <michele.curti@gmail.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
John Lin <john.lin@realtek.com>, Bard Liao <bardliao@realtek.com>,
Flove <flove@realtek.com>
Subject: Re: [PATCH] ASoC: rt5645: move RT5650 muxes to rt5650_specific_dapm_widgets
Date: Mon, 15 Jun 2015 16:12:47 +0100 [thread overview]
Message-ID: <20150615151247.GS18309@sirena.org.uk> (raw)
In-Reply-To: <7EB0DE829A537248AF2ED30C97D12694F802B8@RTITMBSV03.realtek.com.tw>
[-- Attachment #1.1: Type: text/plain, Size: 687 bytes --]
On Mon, Jun 15, 2015 at 10:29:56AM +0000, Oder Chiou wrote:
> > Did Michele write this patch or did you? It doesn't matter so much when
> > all the signoffs come from within the same company but given that
> > Michele has a gmail rather than Realtek address the licensing parts of
> > the signoff start to matter.
> The patch was written by Michele. She sent the patch to us and
> alsa-devel@alsa-project.org, but the mail address was not included you.
> So we forwarded the patch, thanks.
If you are forwarding on a patch that someone else wrote it is *very*
important that you preserve their authorship, sending a From: line as
part of the patch (as covered in SubmittingPatches).
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-06-15 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 2:44 [PATCH] ASoC: rt5645: move RT5650 muxes to rt5650_specific_dapm_widgets Oder Chiou
2015-06-15 10:04 ` Mark Brown
2015-06-15 10:29 ` Oder Chiou
2015-06-15 15:04 ` Michele Curti
2015-06-15 15:12 ` Mark Brown [this message]
2015-06-15 19:10 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2015-06-12 9:59 [PATCH] ASoc: " Michele Curti
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=20150615151247.GS18309@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=flove@realtek.com \
--cc=john.lin@realtek.com \
--cc=lgirdwood@gmail.com \
--cc=michele.curti@gmail.com \
--cc=oder_chiou@realtek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.