bpf: Remove redundant __GFP_NOWARN #5679
Closed
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
Author
|
Upstream branch: f3af62b |
Author
|
Upstream branch: f3af62b |
kernel-patches-daemon-bpf-rc
bot
force-pushed
the
series/988125=>bpf-next
branch
from
ef0060f to
ffb43a6
Compare
kernel-patches-daemon-bpf-rc
bot
force-pushed
the
bpf-next_base
branch
4 times, most recently
from
51c6121 to
ed19bc9
Compare
Author
|
Upstream branch: f3af62b |
kernel-patches-daemon-bpf-rc
bot
force-pushed
the
series/988125=>bpf-next
branch
from
ffb43a6 to
a4cb9c6
Compare
kernel-patches-daemon-bpf-rc
bot
force-pushed
the
bpf-next_base
branch
from
ed19bc9 to
1a33a8f
Compare
Author
|
Upstream branch: 911c035 |
kernel-patches-daemon-bpf-rc
bot
force-pushed
the
series/988125=>bpf-next
branch
from
a4cb9c6 to
78d5900
Compare
kernel-patches-daemon-bpf-rc
bot
added
V1-ci-fail
V1-ci-pass
and removed
V1-ci-pass
V1-ci-fail
labels
kernel-patches-daemon-bpf-rc
bot
added
V1-ci-pass
V1-ci-fail
and removed
V1-ci-fail
V1-ci-pass
labels
kernel-patches-daemon-bpf-rc
bot
force-pushed
the
bpf-next_base
branch
from
8821f0b to
71f5f86
Compare
Author
|
Upstream branch: fa47913 |
kernel-patches-daemon-bpf-rc
bot
force-pushed
the
series/988125=>bpf-next
branch
from
e5b6a99 to
ee53759
Compare
kernel-patches-daemon-bpf-rc
bot
force-pushed
the
bpf-next_base
branch
from
71f5f86 to
32bec89
Compare
Commit 16f5dfb ("gfp: include __GFP_NOWARN in GFP_NOWAIT") made GFP_NOWAIT implicitly include __GFP_NOWARN. Therefore, explicit __GFP_NOWARN combined with GFP_NOWAIT (e.g., `GFP_NOWAIT | __GFP_NOWARN`) is now redundant. Let's clean up these redundant flags across subsystems. No functional changes. Signed-off-by: Qianfeng Rong <[email protected]> Acked-by: Jiri Olsa <[email protected]>
Author
|
Upstream branch: 9e293d4 |
kernel-patches-daemon-bpf-rc
bot
force-pushed
the
series/988125=>bpf-next
branch
from
ee53759 to
81a92c7
Compare
kernel-patches-daemon-bpf-rc
bot
force-pushed
the
bpf-next_base
branch
from
32bec89 to
88bd43a
Compare
Author
|
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=988125 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: bpf: Remove redundant __GFP_NOWARN
version: 1
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=988125