Skip to content
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

lkl: Remove CONFIG_EVENTFD in hijack init.c #180

Merged
1 commit merged into from
Jul 22, 2016
Merged

Conversation

liuyuan10
Copy link
Member

@liuyuan10 liuyuan10 commented Jul 21, 2016

CONFIG_EVENTFD has been a default config

Signed-off-by: Yuan Liu liuyuan@google.com


This change is Reviewable

CONFIG_EVENTFD has been a default config

Signed-off-by: Yuan Liu <liuyuan@google.com>
@ghost
Copy link

ghost commented Jul 22, 2016

Even if CONFIG_EVENTFD is on by default, it could be changed by a custom config, so I think we should keep the ifdef.

Also, since this was added by @pscollins , I want to know his opinion as well.

@pscollins
Copy link
Member

Fine by me either way --- IIRC the problem I was trying to fix with this was better solved by adding fixup_netdev_linux_fdnet_ops() in hijack/init.c, so the ifdef isn't needed anymore.

@liuyuan10
Copy link
Member Author

The real problem here is that CONFIG_EVNETFD is not passed to hijack even if it's enabled. So there is no reason to keep it IMO.

@ghost
Copy link

ghost commented Jul 22, 2016

The real problem here is that CONFIG_EVNETFD is not passed to hijack even if it's enabled. So there is no reason to keep it IMO

Good point. Lets remove it then.

@ghost ghost merged commit d171188 into lkl:master Jul 22, 2016
@liuyuan10 liuyuan10 deleted the eventfd branch July 22, 2016 16:43
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants