From: Kim Phillips <kim.phillips@freescale.com>
To: "J. German Rivera" <German.Rivera@freescale.com>
Cc: <gregkh@linuxfoundation.org>, <arnd@arndb.de>,
<linux-kernel@vger.kernel.org>, <stuart.yoder@freescale.com>,
<scottwood@freescale.com>, <agraf@suse.de>,
<linuxppc-release@linux.freescale.net>
Subject: Re: [PATCH 0/3 v2] drivers/bus: Freescale Management Complex bus driver patch series
Date: Mon, 22 Sep 2014 11:53:28 -0500 [thread overview]
Message-ID: <20140922115328.7d6fa30635ed52de425f9ebc@freescale.com> (raw)
In-Reply-To: <1411166981-3610-1-git-send-email-German.Rivera@freescale.com>
On Fri, 19 Sep 2014 17:49:38 -0500
"J. German Rivera" <German.Rivera@freescale.com> wrote:
> CHANGE HISTORY
>
> Issues pending resolution not addressed by v2:
> - What to do with Doxygen comments in patch 1
It's clear they should be removed.
> - Whether to move or not FSL-specific header files added in include/linux,
> by this patch series, to another location
there wasn't a valid objection against moving them under fsl/ and
changing them to use dashes instead of underscores, was there?
> - Whether to change or not the wording of the licenses used in some
> source files
I agree with Alex to use the existing kernel versions, to be on
the safe side, but IANAL - did you want to go to the source of the
change (presumably a lawyer?) and find out why the contributors
clause was omitted and how they think that's appropriate in an
upstream submission? If not, please resubmit after converting all
files to use the existing common kernel license text.
Thanks,
Kim
next prev parent reply other threads:[~2014-09-22 16:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 22:49 J. German Rivera
2014-09-19 22:49 ` [PATCH 1/3 v2] drivers/bus: Added Freescale Management Complex APIs J. German Rivera
2014-09-24 0:49 ` Kim Phillips
2014-09-25 2:23 ` German Rivera
2014-09-25 3:40 ` Kim Phillips
2014-09-25 15:44 ` German Rivera
2014-09-25 16:16 ` Scott Wood
2014-09-25 16:44 ` German Rivera
2014-09-25 20:05 ` Scott Wood
2014-09-19 22:49 ` [PATCH 2/3 v2] drivers/bus: Freescale Management Complex (fsl-mc) bus driver J. German Rivera
2014-09-19 22:49 ` [PATCH 3/3 v2] drivers/bus: Device driver for FSL-MC DPRC devices J. German Rivera
2014-10-01 2:19 ` Timur Tabi
2014-10-01 2:27 ` Scott Wood
2014-10-01 2:35 ` Timur Tabi
2014-10-02 16:36 ` German Rivera
2014-10-02 17:19 ` Timur Tabi
2014-09-22 16:53 ` Kim Phillips [this message]
2014-09-22 17:59 ` [PATCH 0/3 v2] drivers/bus: Freescale Management Complex bus driver patch series Stuart Yoder
2014-09-22 22:03 ` Kim Phillips
2014-09-23 14:52 ` German Rivera
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=20140922115328.7d6fa30635ed52de425f9ebc@freescale.com \
--to=kim.phillips@freescale.com \
--cc=German.Rivera@freescale.com \
--cc=agraf@suse.de \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-release@linux.freescale.net \
--cc=scottwood@freescale.com \
--cc=stuart.yoder@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®