All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Daniel Drake <drake@endlessm.com>
Cc: alsa-devel@alsa-project.org,
	Linux Upstreaming Team <linux@endlessm.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	yangxiaohua <yangxiaohua@everest-semi.com>,
	Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 1/2] ASoC: add es8316 codec driver
Date: Sun, 14 May 2017 18:36:02 +0900	[thread overview]
Message-ID: <20170514093602.fzvy44vdej3ukyym@sirena.org.uk> (raw)
In-Reply-To: <CAD8Lp47DsghwLrdn3izM63BCqn56=esdNeKV6L4NU9tdRhNPQg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 898 bytes --]

On Wed, May 10, 2017 at 01:18:20PM -0600, Daniel Drake wrote:
> 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?

I'm not going to look at patches that don't have signoffs, sorry.
Please see SubmittingPatches for details of what a signoff means and how
to handle them.  Without knowing how closely what you've done resembles
what you're basing it on it's hard to be sure.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2017-05-15  7:56 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
2017-05-14  9:36     ` Mark Brown [this message]

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=20170514093602.fzvy44vdej3ukyym@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=drake@endlessm.com \
    --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.