Page MenuHomeFreeBSD

ifnet: Integrate if_unroute() into if_down()
AcceptedPublic

Authored by zlei on Fri, Mar 14, 11:48 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Mar 17, 7:03 PM
Unknown Object (File)
Mon, Mar 17, 4:32 AM
Unknown Object (File)
Sun, Mar 16, 4:23 AM
Unknown Object (File)
Sun, Mar 16, 3:26 AM
Unknown Object (File)
Sun, Mar 16, 12:54 AM
Subscribers

Details

Reviewers
glebius
melifaro
Group Reviewers
network
Summary

if_unroute() is static since 2004 and is not used anywhere except for
if_down().

This also makes it easier to grep by the pattern if_flags &= ~IFF_UP.

No functional change intended.

MFC after: 1 week

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

zlei requested review of this revision.Fri, Mar 14, 11:48 AM

Thanks!

I have only light concerns with aggressive MFC plan on refactoring changes. Sometimes bugs sneak into refactorings that seems to be innocent. Whether to MFC or not is almost always is up to decision of merging committer. My personal take is that I would MFC refactoring changes only if they are a prerequisite for a following bugfix or a new driver/module that goes to a stable branch.

This revision is now accepted and ready to land.Fri, Mar 14, 4:47 PM

Thanks!

I have only light concerns with aggressive MFC plan on refactoring changes. Sometimes bugs sneak into refactorings that seems to be innocent.

Yeah, I think I have checked that carefully. For this case, I checked the usage of if_unroute() from -current to stable/8.

Whether to MFC or not is almost always is up to decision of merging committer. My personal take is that I would MFC refactoring changes only if they are a prerequisite for a following bugfix or a new driver/module that goes to a stable branch.

Valid point. Well I tend to MFC if possible, mainly to reduce the drift between stable branches, and it is easier to filter out critical changes between branches.

Anyway I'll do that carefully.