From: Pavel Machek <pavel@ucw.cz>
To: ofono@ofono.org
Subject: Re: [RFC PATCH] new gemalto plugin
Date: Wed, 31 Oct 2018 19:03:22 +0100 [thread overview]
Message-ID: <20181031180322.GA29388@amd> (raw)
In-Reply-To: <CAKSBH7FiSURgggfqPnBK-LEOPzZc8D6Et-RKHvt7Orimn5Tvqw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
Hi!
> > Also, there are security and interference aspects to consider. One can
> > send some AT command that interferes with the functioning of an atom
> > driver for example and then your entire system breaks. Trust me, it is
> > just not a good idea. If you want to shoot yourself in the foot, be my
> > guest. But it isn't going upstream ;)
>
> it's ok, GPLv2 just requires me to publish the changes I have done to
> the code, not to fight to get them upstream.
Actually, GPLv2 does not you require to publish your changes.
It just (approximately) means that if you give binaries to someone, you give them
sources, too...
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-10-31 18:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 6:10 [RFC PATCH] new gemalto plugin Giacinto Cifelli
2018-10-29 19:58 ` Denis Kenzior
2018-10-30 6:10 ` Giacinto Cifelli
2018-10-30 15:23 ` Denis Kenzior
2018-10-31 6:55 ` Giacinto Cifelli
2018-10-31 18:03 ` Pavel Machek [this message]
2018-10-31 19:45 ` Giacinto Cifelli
2018-10-31 18:42 ` Denis Kenzior
2018-10-31 19:07 ` Marcel Holtmann
2018-10-31 19:23 ` Denis Kenzior
2018-10-31 19:44 ` Giacinto Cifelli
2018-10-31 19:56 ` Giacinto Cifelli
2018-10-31 20:15 ` Denis Kenzior
2018-10-31 20:19 ` Marcel Holtmann
2018-10-31 20:32 ` Giacinto Cifelli
2018-10-31 21:16 ` Denis Kenzior
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=20181031180322.GA29388@amd \
--to=pavel@ucw.cz \
--cc=ofono@ofono.org \
/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.