-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More if zero #7974
More if zero #7974
Conversation
The #if 0 code in ospfd, has not been compiled since at least 2012. If we are at least 9 years old at this point with no effort to use or save, we should just get rid of it. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
The earliest that some of this code is 2018. There is not much point in keeping this code around. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Old dead code. Like a log jamming your build system Signed-off-by: Donald Sharp <sharpd@nvidia.com>
rip, ripped out the #if 0 code. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Remove some more dead code. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Looks like the #if 0 code in this place was for ESI support on solaris. We do not support solaris anymore. So let's remove with prejudice. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Remove all dead #if 0 code from bgpd. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
We do have a bunch of old code that is never used. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
There is some dead code in eigrpd Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Just some more dead code that has been sitting unused for a very long time. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
I am not even sure what the goal of this code was in any way shape fashion or form. But since it's pbr_nht.c I as the original author should know... But I don't. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
/* | ||
* bpacket_queue_sanity_check | ||
*/ | ||
void bpacket_queue_sanity_check(struct bpacket_queue __attribute__((__unused__)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh man - I don't know the specifics here, but I love a sanity check. maybe it could be under some more useful ifdef, so it's not entirely lost? or is it really adding ... nothing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one didn't even compile anymore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can put it back, as that I struggled with this one in all honesty. If we are not even taking the time to make sure it works now. What is it going to be like in another year or so?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, you're right - if it's not being maintained, it's not going to be "easy" to turn on and use.
ospfd/ospfd.c
Outdated
@@ -2004,29 +1984,9 @@ struct ospf_nbr_nbma *ospf_nbr_nbma_lookup(struct ospf *ospf, | |||
struct ospf_nbr_nbma *ospf_nbr_nbma_lookup_next(struct ospf *ospf, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so ... looks like this api always just returns NULL now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well I would say it's returned NULL since 2002. I go back through and just clean this up a bit more in a sec here.
The calling function of ospf_nbr_nbma_lookup_next calls this function and then immediately returns when it gets the NULL. Just cleanup a bit more code. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Continuous Integration Result: SUCCESSFULContinuous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-FRRPULLREQ-16810/ This is a comment from an automated CI system. Warnings Generated during build:Checkout code: Successful with additional warnings
Warnings Generated during build:Debian 10 amd64 build: Successful with additional warningsDebian Package lintian failed for Debian 10 amd64 build:
|
Continuous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-FRRPULLREQ-16811/ This is a comment from an automated CI system. Warnings Generated during build:Checkout code: Successful with additional warnings
Warnings Generated during build:Debian 10 amd64 build: Successful with additional warningsDebian Package lintian failed for Debian 10 amd64 build:
|
💚 Basic BGPD CI results: SUCCESS, 0 tests failedResults table
For details, please contact louberger |
lots of #if 0 code in the code base. Remove a large chunk.