From: Patrick McHardy <kaber@trash.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: pablo@netfilter.org, davem@davemloft.net, tgraf@suug.ch,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] netfilter: preparatory patches for set extensions
Date: Sun, 22 Mar 2015 04:48:46 +0000 [thread overview]
Message-ID: <20150322044846.GB31192@acer.localdomain> (raw)
In-Reply-To: <20150321230447.GA31869@gondor.apana.org.au>
On 22.03, Herbert Xu wrote:
> On Sat, Mar 21, 2015 at 03:38:08PM +0000, Patrick McHardy wrote:
> >
> > @Dave and Pablo: these patches apply on top of nf-next and a bunch
> > of patches I just sent to Pablo, but also need Herbert's recent
> > changes in net-next. Additionally I have more patches coming up
> > which depend on these changes. In order to simplify things, I'd
> > suggest to have the rhashtable change go through Pablo's tree if
> > you don't mind.
>
> I have more patches (multiple rehashing) coming up that will
> conflict with this.
I have a set of about 30 patches myself which depend on this simple
one liner, so I'd appreciate if we can come to a quick resolution
here so I can continue merging them instead of redoing them every
second day.
next prev parent reply other threads:[~2015-03-22 4:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 15:38 [PATCH 0/2] netfilter: preparatory patches for set extensions Patrick McHardy
2015-03-21 15:38 ` [PATCH 1/2] rhashtable: provide len to obj_hashfn Patrick McHardy
2015-03-21 23:06 ` Herbert Xu
2015-03-22 4:47 ` Patrick McHardy
2015-03-22 7:22 ` Herbert Xu
2015-03-22 7:31 ` Patrick McHardy
2015-03-22 10:39 ` Thomas Graf
2015-03-21 15:38 ` [PATCH 2/2] netfilter: nft_hash: convert to use rhashtable callbacks Patrick McHardy
2015-03-21 23:04 ` [PATCH 0/2] netfilter: preparatory patches for set extensions Herbert Xu
2015-03-22 4:48 ` Patrick McHardy [this message]
2015-03-23 20:44 ` David Miller
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=20150322044846.GB31192@acer.localdomain \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=tgraf@suug.ch \
/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