From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] is it worth contributing a SATA SIL3512 driver to u-boot?
Date: Thu, 10 Dec 2015 15:19:16 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.20.1512101518110.3369@localhost> (raw)
In-Reply-To: <CAOMZO5AvLr=DAvNyKLEK6fdUOBOnprRxWxvydW0tQa-m7aLn_g@mail.gmail.com>
On Thu, 10 Dec 2015, Fabio Estevam wrote:
> On Thu, Dec 10, 2015 at 4:14 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> >
> > on current project, someone handed me a patch containing (among
> > other thigns) source and header files for support for SATA SIL3512 --
> > copyright shows they're under GPL. rather than carrying around that
> > part of the patch, is it worth simply handing that over to u-boot to
> > add under drivers/block/?
>
> Yes, feel free to submit it, but please make sure there is an user for
> this driver as well.
well, the contract i'm working on will be using it for porting linux
to a *lot* of older platforms so, technically, i'm that user. :-)
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2015-12-10 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 18:14 [U-Boot] is it worth contributing a SATA SIL3512 driver to u-boot? Robert P. J. Day
2015-12-10 18:56 ` Fabio Estevam
2015-12-10 20:19 ` Robert P. J. Day [this message]
2015-12-10 21:23 ` Fabio Estevam
2015-12-10 21:25 ` Robert P. J. Day
2015-12-11 12:16 ` Robert P. J. Day
2015-12-11 12:37 ` Michal Suchanek
2015-12-13 13:37 ` Robert P. J. Day
2015-12-13 18:34 ` Fabio Estevam
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=alpine.LFD.2.20.1512101518110.3369@localhost \
--to=rpjday@crashcourse.ca \
--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.