From: Johan Hovold <johan@kernel.org>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: Johan Hovold <johan@kernel.org>, Karoly Pados <pados@pados.hu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Martyn Welch <martyn.welch@collabora.co.uk>
Subject: USB: serial: cp210x: Implement GPIO support for CP2102N
Date: Thu, 5 Jul 2018 15:10:27 +0200 [thread overview]
Message-ID: <20180705131027.GB9802@localhost> (raw)
On Mon, Jul 02, 2018 at 08:04:32PM +0200, Bjørn Mork wrote:
> Johan Hovold <johan@kernel.org> writes:
>
> >> Not quite. It is not from a forum post, but from a SiLabs Knowledge
> >> Base article
> >> (https://www.silabs.com/community/interface/knowledge-base.entry.html/2017/06/12/fletcher_checksumfo-TeDF)
> >
> > Yeah, that's the one I was referring to.
> >
> >> That article states explicitly that the code was taken from Wikipedia,
> >> so it is CC-SA, which is to the best of my knowledge 1) compatible
> >> with GPL, and 2) does not require attribution if the original material
> >> is missing it, and it does. So AFAICT we are clear on the licensing
> >> front.
> >
> > First of all I can't seem to find that code snippet on the wiki page it
> > does refer to, so I'm still not convinced.
>
> It was there in older versions of the article. See for example:
> https://en.wikipedia.org/w/index.php?title=Fletcher%27s_checksum&oldid=730327006
Ah, thanks for digging that out.
> > Second, this should have been high-lighted in your submission somehow.
>
> Definitely. All code has an original author who deserves credit. And if
> you cannot find the original author, then there is always a risk than
> someone along the line stole the code... Maybe long before it ended up
> in Wikipedia. But that doesn't matter.
>
> Doesn't seem worth the risk for a simple checksum algorithm which
> probably has lots of GPL implementations.
Right.
Johan
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Johan Hovold <johan@kernel.org>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: Johan Hovold <johan@kernel.org>, Karoly Pados <pados@pados.hu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Martyn Welch <martyn.welch@collabora.co.uk>
Subject: Re: [PATCH] USB: serial: cp210x: Implement GPIO support for CP2102N
Date: Thu, 5 Jul 2018 15:10:27 +0200 [thread overview]
Message-ID: <20180705131027.GB9802@localhost> (raw)
In-Reply-To: <87d0w5wm33.fsf@miraculix.mork.no>
On Mon, Jul 02, 2018 at 08:04:32PM +0200, Bjørn Mork wrote:
> Johan Hovold <johan@kernel.org> writes:
>
> >> Not quite. It is not from a forum post, but from a SiLabs Knowledge
> >> Base article
> >> (https://www.silabs.com/community/interface/knowledge-base.entry.html/2017/06/12/fletcher_checksumfo-TeDF)
> >
> > Yeah, that's the one I was referring to.
> >
> >> That article states explicitly that the code was taken from Wikipedia,
> >> so it is CC-SA, which is to the best of my knowledge 1) compatible
> >> with GPL, and 2) does not require attribution if the original material
> >> is missing it, and it does. So AFAICT we are clear on the licensing
> >> front.
> >
> > First of all I can't seem to find that code snippet on the wiki page it
> > does refer to, so I'm still not convinced.
>
> It was there in older versions of the article. See for example:
> https://en.wikipedia.org/w/index.php?title=Fletcher%27s_checksum&oldid=730327006
Ah, thanks for digging that out.
> > Second, this should have been high-lighted in your submission somehow.
>
> Definitely. All code has an original author who deserves credit. And if
> you cannot find the original author, then there is always a risk than
> someone along the line stole the code... Maybe long before it ended up
> in Wikipedia. But that doesn't matter.
>
> Doesn't seem worth the risk for a simple checksum algorithm which
> probably has lots of GPL implementations.
Right.
Johan
next reply other threads:[~2018-07-05 13:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 13:10 Johan Hovold [this message]
2018-07-05 13:10 ` [PATCH] USB: serial: cp210x: Implement GPIO support for CP2102N Johan Hovold
-- strict thread matches above, loose matches on Subject: below --
2018-07-05 13:11 Johan Hovold
2018-07-05 13:11 ` [PATCH] " Johan Hovold
2018-07-05 13:09 Johan Hovold
2018-07-05 13:09 ` [PATCH] " Johan Hovold
2018-07-02 19:17 Karoly Pados
2018-07-02 19:17 ` [PATCH] " Karoly Pados
2018-07-02 18:04 Bjørn Mork
2018-07-02 18:04 ` [PATCH] " Bjørn Mork
2018-06-22 15:10 Martyn Welch
2018-06-22 15:10 ` [PATCH] " Martyn Welch
2018-06-20 19:41 Karoly Pados
2018-06-20 19:41 ` [PATCH] " Karoly Pados
2018-06-20 16:51 Martyn Welch
2018-06-20 16:51 ` [PATCH] " Martyn Welch
2018-06-20 10:52 Johan Hovold
2018-06-20 10:52 ` [PATCH] " Johan Hovold
2018-06-20 9:45 Karoly Pados
2018-06-20 9:45 ` [PATCH] " Karoly Pados
2018-06-20 8:25 Johan Hovold
2018-06-20 8:25 ` [PATCH] " Johan Hovold
2018-06-17 18:25 Karoly Pados
2018-06-17 18:25 ` [PATCH] " Karoly Pados
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=20180705131027.GB9802@localhost \
--to=johan@kernel.org \
--cc=bjorn@mork.no \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=martyn.welch@collabora.co.uk \
--cc=pados@pados.hu \
/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.