libbpf: fix the incorrect reference to the memlock_rlim variable in the comment. #10108
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Upstream branch: e758657 |
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
ecdeefe to
10ce4bd
Compare
|
Upstream branch: ff88079 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/1016032=>bpf-next
branch
from
a77afc6 to
0a3ae1a
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
10ce4bd to
e5828a2
Compare
|
Upstream branch: f9db3a3 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/1016032=>bpf-next
branch
from
0a3ae1a to
b5d1301
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
e5828a2 to
13927c8
Compare
|
Upstream branch: 8842732 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/1016032=>bpf-next
branch
from
b5d1301 to
2aacb66
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
13927c8 to
9b73883
Compare
|
Upstream branch: 23f852d |
…he comment. The variable "memlock_rlim_max" referenced in the comment does not exist. I think that the author probably meant the variable "memlock_rlim". So, correct it. Signed-off-by: Jianyun Gao <[email protected]>
kernel-patches-daemon-bpf
bot
force-pushed
the
series/1016032=>bpf-next
branch
from
2aacb66 to
9e9763a
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
9b73883 to
3cfe497
Compare
|
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=1016032 irrelevant now. Closing PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull request for series with
subject: libbpf: fix the incorrect reference to the memlock_rlim variable in the comment.
version: 1
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=1016032