From: Mark Brown <broonie@kernel.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Bayyavarapu, Maruthi" <maruthi.bayyavarapu@amd.com>,
Takashi Iwai <tiwai@suse.de>, Liam Girdwood <lgirdwood@gmail.com>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
Alex Deucher <alexander.deucher@amd.com>,
Dave Airlie <airlied@gmail.com>
Subject: Re: [PATCH 3/3] ASoC: AMD: add AMD ASoC ACP-I2S driver [v4]
Date: Thu, 20 Aug 2015 15:31:13 -0700 [thread overview]
Message-ID: <20150820223113.GW12027@sirena.org.uk> (raw)
In-Reply-To: <CADnq5_NOd_JLafdvbCs3oVGhDPZC+dD1xD_hL1R8+qaMgr2i3w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1718 bytes --]
On Thu, Aug 20, 2015 at 05:30:27PM -0400, Alex Deucher wrote:
> On Thu, Aug 20, 2015 at 5:13 PM, Mark Brown <broonie@kernel.org> wrote:
> >> v4: squash in naming fixes
> > To repeat what I said last time:
> > | Please follow the patch submission process in SubmittingPatches: put any
> > | versioning in the subject line inside the [] and put noise like inter
> > | version changelogs after the ---.
> I addressed this in my coverletter. Some subsystems prefer to retain
> that information. If you'd prefer to not have them in the audio patch
> I will remove them.
When I said to follow the standard process here that's what I meant,
yes. It's basically just the graphics subsystem that does something
different here, and note that if you are going to include a changelog
(either in the normal place or the DRM place) it really ought to
actually describe the changes that have been made - the above doesn't
reflect the changes that were made at all.
> > I also remain very concerned about this non-GPL license you are using.
> > Please do not ignore review comments like this :(
> I mentioned this in the cover letter as well. Most if not all of the
> drm drivers are licensed the same way. IANAL, but I am not aware of
> any concerns about them.
DRM is a special case here since there has always been work to share
bits of the code with other operating systems, the licensing for DRM is
very unusual within the kernel. A quick sampling of drivers suggests
that this license is not universally used there either.
There is also the issue I raised with the fact that your non-GPL license
statement does not appear to correspond to the MODULE_LICENSE() that
you've included which claims the code is GPLed.
[-- 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-08-20 22:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 20:09 [PATCH 0/3] Add ASoC support for AMD APUs [v2] Alex Deucher
2015-08-20 20:09 ` [PATCH 2/3] drm/amd: add ACP driver support [v6] Alex Deucher
2015-08-20 20:09 ` [PATCH 3/3] ASoC: AMD: add AMD ASoC ACP-I2S driver [v4] Alex Deucher
2015-08-20 21:13 ` Mark Brown
2015-08-20 21:30 ` Alex Deucher
2015-08-20 22:31 ` Mark Brown [this message]
2015-08-20 23:11 ` Alex Deucher
2015-08-20 23:45 ` Mark Brown
2015-08-20 23:50 ` Alex Deucher
2015-08-21 0:10 ` Mark Brown
2015-08-21 2:05 ` Alex Deucher
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=20150820223113.GW12027@sirena.org.uk \
--to=broonie@kernel.org \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=lgirdwood@gmail.com \
--cc=maruthi.bayyavarapu@amd.com \
--cc=tiwai@suse.de \
/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