From: Thomas Graf <tgraf@suug.ch>
To: Patrick McHardy <kaber@trash.net>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, paulmck@linux.vnet.ibm.com,
josh@joshtriplett.org, challa@noironetworks.com,
walpole@cs.pdx.edu, dev@openvswitch.org, tklauser@distanz.ch,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH net-next 1/3] lib: Resizable, Scalable, Concurrent Hash Table
Date: Fri, 1 Aug 2014 11:32:55 +0100 [thread overview]
Message-ID: <20140801103255.GA7331@casper.infradead.org> (raw)
In-Reply-To: <20140801102632.GA19476@server.your-server.de>
On 08/01/14 at 12:26pm, Patrick McHardy wrote:
> On Fri, Aug 01, 2014 at 10:51:58AM +0200, Thomas Graf wrote:
> > --- /dev/null
> > +++ b/include/linux/rhashtable.h
> > @@ -0,0 +1,213 @@
> > +/*
> > + * Resizable, Scalable, Concurrent Hash Table
> > + *
> > + * Copyright (c) 2014 Thomas Graf <tgraf@suug.ch>
> > + *
> > + * Based on the following paper by Josh Triplett, Paul E. McKenney
> > + * and Jonathan Walpole:
> > + * https://www.usenix.org/legacy/event/atc11/tech/final_files/Triplett.pdf
> > + *
> > + * Code partially derived from nft_hash:
> > + * Copyright (c) 2008-2014 Patrick McHardy <kaber@trash.net>
>
> Minor request: german copyright law as an assumption of authorship for
> authors marked in the work. When doing GPL enforcement I would prefer
> any discussions about what derived from specifically means in this
> case and whether this constitutes a normal statement of authorship,
> and since this clearly contains a lot of literal code I have written,
> please change this to something like
>
> Copyright ... Thomas Graf
> Copyright ... Patrick McHardy
>
> ...
>
> Code partially derived from nft_hash.
>
> Thanks!
Sure, it was not my intention to hide ownership in any way.
next prev parent reply other threads:[~2014-08-01 10:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 8:51 [PATCH net-next v3 0/3] Lockless netlink_lookup() with new concurrent hash table Thomas Graf
2014-08-01 8:51 ` [PATCH net-next 1/3] lib: Resizable, Scalable, Concurrent Hash Table Thomas Graf
2014-08-01 10:01 ` Nikolay Aleksandrov
2014-08-01 10:33 ` Thomas Graf
2014-08-01 10:26 ` Patrick McHardy
2014-08-01 10:32 ` Thomas Graf [this message]
2014-08-01 8:51 ` [PATCH net-next 2/3] netlink: Convert netlink_lookup() to use RCU protected hash table Thomas Graf
2014-08-01 8:52 ` [PATCH net-next 3/3] nftables: Convert nft_hash to use generic rhashtable Thomas Graf
2014-08-01 10:17 ` Patrick McHardy
2014-08-01 10:39 ` Thomas Graf
2014-08-01 10:47 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2014-08-02 9:47 [PATCH net-next v5 0/3] Lockless netlink_lookup() with new concurrent hash table Thomas Graf
2014-08-02 9:47 ` [PATCH net-next 1/3] lib: Resizable, Scalable, Concurrent Hash Table Thomas Graf
2014-08-02 10:32 ` Nikolay Aleksandrov
2014-08-01 11:58 [PATCH net-next v4 0/3] Lockless netlink_lookup() with new concurrent hash table Thomas Graf
2014-08-01 11:58 ` [PATCH net-next 1/3] lib: Resizable, Scalable, Concurrent Hash Table Thomas Graf
2014-07-31 22:56 [PATCH v2 0/3 net-next] Lockless netlink_lookup() with new concurrent hash table Thomas Graf
2014-07-31 22:56 ` [PATCH net-next 1/3] lib: Resizable, Scalable, Concurrent Hash Table Thomas Graf
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=20140801103255.GA7331@casper.infradead.org \
--to=tgraf@suug.ch \
--cc=challa@noironetworks.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=josh@joshtriplett.org \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tklauser@distanz.ch \
--cc=walpole@cs.pdx.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).