From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] drivers/ddr/fsl: Dual-license DDR driver
Date: Mon, 12 Feb 2018 18:51:29 -0500 [thread overview]
Message-ID: <20180212235129.GM10592@bill-the-cat> (raw)
In-Reply-To: <VI1PR04MB20785EF7D2578E39C048EE219AF70@VI1PR04MB2078.eurprd04.prod.outlook.com>
On Mon, Feb 12, 2018 at 10:51:10PM +0000, York Sun wrote:
> On 02/12/2018 02:44 PM, Marek Vasut wrote:
> > On 02/12/2018 11:41 PM, York Sun wrote:
> >> On 02/07/2018 11:48 AM, York Sun wrote:
> >>> To make this driver easier to be reused, dual-license DDR driver.
> >>>
> >>> Signed-off-by: York Sun <york.sun@nxp.com>
> >>> CC: Simon Glass <sjg@chromium.org>
> >>> CC: Tom Rini <trini@konsulko.com>
> >>> CC: Heinrich Schuchardt <xypron.glpk@gmx.de>
> >>> CC: Thomas Schaefer <thomas.schaefer@kontron.com>
> >>> CC: Masahiro Yamada <yamada.masahiro@socionext.com>
> >>> CC: Robert P. J. Day <rpjday@crashcourse.ca>
> >>> CC: Alexander Merkle <alexander.merkle@lauterbach.com>
> >>> CC: Joakim Tjernlund <joakim.tjernlund@transmode.se>
> >>> CC: Curt Brune <curt@cumulusnetworks.com>
> >>> CC: Valentin Longchamp <valentin.longchamp@keymile.com>
> >>> CC: Wolfgang Denk <wd@denx.de>
> >>> CC: Anatolij Gustschin <agust@denx.de>
> >>> CC: Ira W. Snyder <iws@ovro.caltech.edu>
> >>> CC: Marek Vasut <marek.vasut@gmail.com>
> >>> CC: Kyle Moffett <Kyle.D.Moffett@boeing.com>
> >>> CC: Sebastien Carlier <sebastien.carlier@gmail.com>
> >>> CC: Stefan Roese <sr@denx.de>
> >>> CC: Peter Tyser <ptyser@xes-inc.com>
> >>> CC: Paul Gortmaker <paul.gortmaker@windriver.com>
> >>> CC: Peter Tyser <ptyser@xes-inc.com>
> >>> CC: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> >>> ---
> >>>
> >>
> >> Applied to fsl-qoriq master, awaiting upstream.
> >
> > Are you sure you can do that so easily ? Did you get ACK on this from
> > everyone who contributed to that driver ?
>
> Nobody said anything. Some addresses bounced. And most changes made out
> people outside Freescale/NXP are minor changes, except twice the files
> were moved during U-Boot structure change. What options do I have?
So, I saw this when it was posted. Am I pleased to see more code change
license terms? No. Do I expect everyone to agree with this? No. Do I
accept the (nominally) technical arguments made about why this should be
done? Yes. Can I object if someone who feels they do have standing to
object to this objects? No.
Hope this helps.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180212/7290219a/attachment.sig>
next prev parent reply other threads:[~2018-02-12 23:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 19:47 [U-Boot] [PATCH] drivers/ddr/fsl: Dual-license DDR driver York Sun
2018-02-12 22:41 ` York Sun
2018-02-12 22:44 ` Marek Vasut
2018-02-12 22:51 ` York Sun
2018-02-12 23:51 ` Tom Rini [this message]
2018-02-13 12:48 ` Wolfgang Denk
2018-02-13 16:05 ` York Sun
2018-02-13 16:25 ` Peter Tyser
2018-02-13 16:54 ` Joakim Tjernlund
2018-02-13 17:02 ` Ira Snyder
2018-02-13 18:04 ` Curt Brune
2018-02-14 8:50 ` Thomas Schaefer
2018-02-13 16:30 ` York Sun
2018-02-13 16:39 ` Alexander Merkle
2018-02-13 16:42 ` York Sun
2018-02-13 17:00 ` York Sun
2018-02-13 17:07 ` Marek Vasut
2018-02-13 18:32 ` York Sun
2018-02-13 19:16 ` Marek Vasut
2018-02-13 19:33 ` York Sun
2018-02-13 20:09 ` Marek Vasut
2018-02-13 20:14 ` York Sun
2018-02-13 22:02 ` Marek Vasut
2018-02-13 17:11 ` York Sun
2018-02-13 17:32 ` Wolfgang Denk
2018-02-13 17:43 ` Heinrich Schuchardt
2018-02-13 19:51 ` Sebastien
2018-02-13 21:39 ` Anatolij Gustschin
2018-02-14 7:38 ` Stefan Roese
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=20180212235129.GM10592@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.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 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.