From: Jiri Pirko <jiri@resnulli.us>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, kuznet@ms2.inr.ac.ru, jmorris@namei.org,
yoshfuji@linux-ipv6.org, kaber@trash.net,
hannes@stressinduktion.org, bcrl@kvack.org,
gaofeng@cn.fujitsu.com, joe@perches.com,
herbert@gondor.apana.org.au
Subject: Re: [patch net-next 3/5] neigh: store parms type inside the structure
Date: Fri, 6 Dec 2013 21:13:29 +0100 [thread overview]
Message-ID: <20131206201329.GA24971@minipsycho.orion> (raw)
In-Reply-To: <20131206.150840.2078088427369267519.davem@davemloft.net>
Fri, Dec 06, 2013 at 09:08:40PM CET, davem@davemloft.net wrote:
>From: Jiri Pirko <jiri@resnulli.us>
>Date: Fri, 6 Dec 2013 19:29:02 +0100
>
>> There is going to be needed later on to distinguish parms instance
>> between ipv4 and ipv6. So just store the type inside.
>>
>> Signed-off-by: Jiri Pirko <jiri@resnulli.us>
>
>Please just use neigh_parms->tbl->family.
I somehow missed that. Thanks. Will send v2.
>
>Thanks.
next prev parent reply other threads:[~2013-12-06 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 18:28 [patch net-next 0/5] neigh: respect default parms values Jiri Pirko
2013-12-06 18:29 ` [patch net-next 1/5] neigh: convert parms to an array Jiri Pirko
2013-12-06 18:29 ` [patch net-next 2/5] neigh: wrap proc dointvec functions Jiri Pirko
2013-12-06 18:29 ` [patch net-next 3/5] neigh: store parms type inside the structure Jiri Pirko
2013-12-06 20:08 ` David Miller
2013-12-06 20:13 ` Jiri Pirko [this message]
2013-12-06 18:29 ` [patch net-next 4/5] neigh: restore old behaviour of default parms values Jiri Pirko
2013-12-06 18:29 ` [patch net-next 5/5] neigh: ipv6: respect default values set before an address is assigned to device Jiri Pirko
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=20131206201329.GA24971@minipsycho.orion \
--to=jiri@resnulli.us \
--cc=bcrl@kvack.org \
--cc=davem@davemloft.net \
--cc=gaofeng@cn.fujitsu.com \
--cc=hannes@stressinduktion.org \
--cc=herbert@gondor.apana.org.au \
--cc=jmorris@namei.org \
--cc=joe@perches.com \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).