From: Alessandro Rubini <rubini@gnudd.com>
To: linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org,
Juan David Gonzalez Cobas <juan.david.gonzalez.cobas@cern.ch>,
"Emilio G. Cota" <cota@braap.org>,
Samuel Iglesias Gonsalvez <siglesias@igalia.com>
Subject: [PATCH V2 0/2] FMC: resend sample drivers
Date: Tue, 18 Jun 2013 23:27:02 +0200 [thread overview]
Message-ID: <cover.1371589927.git.rubini@gnudd.com> (raw)
As suggested by Greg-KH [1] I'm resending the two example submodules
(one carrier driver and one mezzanine driver) with a proper licence
text for BSD. Among the various wordings, I chose the shortest one, as
used by a number of drivers/net/wireless/ files. Thank you David for
checking the distribution policies.
I rebased to next-20130617 and rebuilt, with no conflicts. In any
of the patches of the original series.
[1] https://lkml.org/lkml/2013/6/17/772:
"Just redo those two patches and send them as 'v2'")
Alessandro Rubini (2):
FMC: add a software carrier driver
FMC: add a software mezzanine driver
Documentation/fmc/00-INDEX | 6 +
Documentation/fmc/fmc-fakedev.txt | 36 ++++
Documentation/fmc/fmc-trivial.txt | 17 ++
drivers/fmc/Kconfig | 18 ++
drivers/fmc/Makefile | 3 +
drivers/fmc/fmc-fakedev.c | 355 +++++++++++++++++++++++++++++++++++++
drivers/fmc/fmc-trivial.c | 107 +++++++++++
7 files changed, 542 insertions(+), 0 deletions(-)
create mode 100644 Documentation/fmc/fmc-fakedev.txt
create mode 100644 Documentation/fmc/fmc-trivial.txt
create mode 100644 drivers/fmc/fmc-fakedev.c
create mode 100644 drivers/fmc/fmc-trivial.c
--
1.7.7.2
next reply other threads:[~2013-06-18 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 21:27 Alessandro Rubini [this message]
2013-06-18 21:27 ` [PATCH V2 1/2] FMC: add a software carrier driver Alessandro Rubini
2013-06-18 21:27 ` [PATCH V2 2/2] FMC: add a software mezzanine driver Alessandro Rubini
2013-06-18 21:36 ` [PATCH V2 0/2] FMC: resend sample drivers Greg KH
2013-06-18 21:38 ` Alessandro Rubini
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=cover.1371589927.git.rubini@gnudd.com \
--to=rubini@gnudd.com \
--cc=cota@braap.org \
--cc=gregkh@linuxfoundation.org \
--cc=juan.david.gonzalez.cobas@cern.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=siglesias@igalia.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.