From: Davidlohr Bueso <dave@stgolabs.net>
To: akpm@linux-foundation.org, torvalds@linux-foundation.org
Cc: manfred@colorfullife.com,
guillaume.knispel@supersonicimagine.com,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: semantics of rhashtable and sysvipc
Date: Wed, 23 May 2018 10:35:31 -0700 [thread overview]
Message-ID: <20180523173531.q7qxm62dkw256nbk@linux-n805> (raw)
In-Reply-To: <20180523172500.anfvmjtumww65ief@linux-n805>
On Wed, 23 May 2018, Davidlohr Bueso wrote:
>I see two possible fixes.
I guess a third option would be to make the hashtable static, but I'm not
against using rhashtables so I'm not really considering this.
next prev parent reply other threads:[~2018-05-23 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 17:25 semantics of rhashtable and sysvipc Davidlohr Bueso
2018-05-23 17:35 ` Davidlohr Bueso [this message]
2018-05-23 18:35 ` Linus Torvalds
2018-05-23 18:31 ` Davidlohr Bueso
2018-05-23 18:52 ` Linus Torvalds
2018-05-23 18:52 ` Davidlohr Bueso
2018-05-24 17:07 ` Davidlohr Bueso
2018-05-24 17:53 ` Linus Torvalds
2018-05-24 18:51 ` Davidlohr Bueso
2018-05-24 19:17 ` Linus Torvalds
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=20180523173531.q7qxm62dkw256nbk@linux-n805 \
--to=dave@stgolabs.net \
--cc=akpm@linux-foundation.org \
--cc=guillaume.knispel@supersonicimagine.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=torvalds@linux-foundation.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 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).