From: David Miller <davem@davemloft.net>
To: tom@herbertland.com
Cc: netdev@vger.kernel.org, kernel-team@fb.com,
roopa@cumulusnetworks.com, tgraf@suug.ch
Subject: Re: [PATCH v2 net-next 0/7] net: ILA resolver and generic resolver backend
Date: Sun, 18 Sep 2016 22:10:24 -0400 (EDT) [thread overview]
Message-ID: <20160918.221024.2210003128839126114.davem@davemloft.net> (raw)
In-Reply-To: <1473974361-2275254-1-git-send-email-tom@herbertland.com>
From: Tom Herbert <tom@herbertland.com>
Date: Thu, 15 Sep 2016 14:19:14 -0700
> This patch set implements an ILA host side resolver. This uses LWT
> to implement the hook to a userspace resolver and tracks pending
> unresolved address using the backend net resolver.
Can you please repost this series with Herbert Xu properly CC:'d
since he maintains rhashtable and is making changes to it recently
which might conflict with what you are proposing here?
Thanks.
next prev parent reply other threads:[~2016-09-19 2:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 21:19 [PATCH v2 net-next 0/7] net: ILA resolver and generic resolver backend Tom Herbert
2016-09-15 21:19 ` [PATCH v2 net-next 1/7] lwt: Add net to build_state argument Tom Herbert
2016-09-15 21:19 ` [PATCH v2 net-next 2/7] spinlock: Add library function to allocate spinlock buckets array Tom Herbert
2016-09-15 21:19 ` [PATCH v2 net-next 3/7] rhashtable: Call library function alloc_bucket_locks Tom Herbert
2016-09-15 21:19 ` [PATCH v2 net-next 4/7] ila: " Tom Herbert
2016-09-15 21:19 ` [PATCH v2 net-next 5/7] rhashtable: abstract out function to get hash Tom Herbert
2016-09-15 21:19 ` [PATCH v2 net-next 6/7] net: Generic resolver backend Tom Herbert
2016-09-15 21:19 ` [PATCH v2 net-next 7/7] ila: Resolver mechanism Tom Herbert
2016-09-19 2:10 ` David Miller [this message]
2016-09-20 9:43 ` [PATCH v2 net-next 0/7] net: ILA resolver and generic resolver backend Herbert Xu
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=20160918.221024.2210003128839126114.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=tgraf@suug.ch \
--cc=tom@herbertland.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 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).