netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dshwatrz@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: fa_type and fib_info - a question
Date: Thu, 27 Jun 2013 16:17:44 -0700 (PDT)	[thread overview]
Message-ID: <20130627.161744.674336032974965021.davem@davemloft.net> (raw)
In-Reply-To: <CAJJAcoeMwSTbSPCQYJa8e5ZNVqWRkP63PzLd3S2bAquD5uZk4g@mail.gmail.com>

From: David Shwatrz <dshwatrz@gmail.com>
Date: Thu, 27 Jun 2013 22:16:12 +0300

> Why does fib_alias contain an fa_type member and also fib_info contain
> a fib_type member?  A fib_alias must refer to some fib_info object via
> the fa_info pointer. Are there cases when fa_type can differ from
> fib_type? or is it so only for some legacy reason?

It's just a simplification that hasn't been done yet.  They should
both be exactly the same and be derived from cfg->fc_type.

      reply	other threads:[~2013-06-27 23:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 19:16 fa_type and fib_info - a question David Shwatrz
2013-06-27 23:17 ` David Miller [this message]

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=20130627.161744.674336032974965021.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dshwatrz@gmail.com \
    --cc=netdev@vger.kernel.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).