From: Daniel Drake <drake@endlessm.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Linux Upstreaming Team <linux@endlessm.com>,
Liam Girdwood <lgirdwood@gmail.com>,
yangxiaohua <yangxiaohua@everest-semi.com>
Subject: Re: [PATCH 1/2] ASoC: add es8316 codec driver
Date: Wed, 10 May 2017 13:18:20 -0600 [thread overview]
Message-ID: <CAD8Lp47DsghwLrdn3izM63BCqn56=esdNeKV6L4NU9tdRhNPQg@mail.gmail.com> (raw)
In-Reply-To: <eb6e6ef4-6022-6d93-a743-051af4826147@linux.intel.com>
On Wed, May 10, 2017 at 12:49 PM, Pierre-Louis Bossart
<pierre-louis.bossart@linux.intel.com> wrote:
> If the copyright is held by Everest Semiconductor and David Yang is also
> from Everest Semiconductor, then a signoff from Everest looks very much
> required?
The original patches from David do now have his sign-off:
https://bugzilla.kernel.org/show_bug.cgi?id=189261#c57
But I have now rearranged things quite a bit. What is the norm here,
can I just copy over the sign off from before, or do we need to
request explicit permission again from David?
Thanks
Daniel
next prev parent reply other threads:[~2017-05-10 19:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 18:16 [PATCH 1/2] ASoC: add es8316 codec driver Daniel Drake
2017-05-10 18:16 ` [PATCH 2/2] ASoC: Intel: add machine driver for BYT/CHT + ES8316 Daniel Drake
2017-05-10 18:49 ` Pierre-Louis Bossart
2017-05-15 18:07 ` Daniel Drake
2017-05-15 18:41 ` Pierre-Louis Bossart
2017-05-10 18:49 ` [PATCH 1/2] ASoC: add es8316 codec driver Pierre-Louis Bossart
2017-05-10 19:18 ` Daniel Drake [this message]
2017-05-14 9:36 ` 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='CAD8Lp47DsghwLrdn3izM63BCqn56=esdNeKV6L4NU9tdRhNPQg@mail.gmail.com' \
--to=drake@endlessm.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux@endlessm.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=yangxiaohua@everest-semi.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.