From: Konrad Djimeli <hidden> Date: 2018-10-04 23:56:24
Fix a simple typo: Completetion -> Completion
Signed-off-by: Konrad Djimeli <redacted>
---
Changes in v2:
- Update line below to be same length as text above
Documentation/networking/af_xdp.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
@@ -159,8 +159,8 @@ log2(2048) LSB of the addr will be masked off, meaning that 2048, 2050 and 3000 refers to the same chunk.-UMEM Completetion Ring-~~~~~~~~~~~~~~~~~~~~~~+UMEM Completion Ring+~~~~~~~~~~~~~~~~~~~~ The Completion Ring is used transfer ownership of UMEM frames from kernel-space to user-space. Just like the Fill ring, UMEM indicies are
From: Björn Töpel <hidden> Date: 2018-10-05 00:33:39
Den tors 4 okt. 2018 kl 19:03 skrev Konrad Djimeli [off-list ref]:
quoted hunk
Fix a simple typo: Completetion -> Completion
Signed-off-by: Konrad Djimeli <redacted>
---
Changes in v2:
- Update line below to be same length as text above
Documentation/networking/af_xdp.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
@@ -159,8 +159,8 @@ log2(2048) LSB of the addr will be masked off, meaning that 2048, 2050 and 3000 refers to the same chunk.-UMEM Completetion Ring-~~~~~~~~~~~~~~~~~~~~~~+UMEM Completion Ring+~~~~~~~~~~~~~~~~~~~~ The Completion Ring is used transfer ownership of UMEM frames from kernel-space to user-space. Just like the Fill ring, UMEM indicies are--
2.17.1
Thanks Konrad! For future patches, you should tag your patch with
'bpf' or 'bpf-next' as pointed out in
Documentation/bpf/bpf_devel_QA.rst. I guess this should go to 'bpf'.
Acked-by: Björn Töpel <redacted>
From: Daniel Borkmann <daniel@iogearbox.net> Date: 2018-10-05 05:09:43
On 10/04/2018 07:38 PM, Björn Töpel wrote:
Den tors 4 okt. 2018 kl 19:03 skrev Konrad Djimeli [off-list ref]:
quoted
Fix a simple typo: Completetion -> Completion
Signed-off-by: Konrad Djimeli <redacted>
---
Changes in v2:
- Update line below to be same length as text above
Documentation/networking/af_xdp.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
@@ -159,8 +159,8 @@ log2(2048) LSB of the addr will be masked off, meaning that 2048, 2050 and 3000 refers to the same chunk.-UMEM Completetion Ring-~~~~~~~~~~~~~~~~~~~~~~+UMEM Completion Ring+~~~~~~~~~~~~~~~~~~~~ The Completion Ring is used transfer ownership of UMEM frames from kernel-space to user-space. Just like the Fill ring, UMEM indicies are--
2.17.1
Thanks Konrad! For future patches, you should tag your patch with
'bpf' or 'bpf-next' as pointed out in
Documentation/bpf/bpf_devel_QA.rst. I guess this should go to 'bpf'.
Acked-by: Björn Töpel <redacted>
I think it's so minor that bpf-next is totally fine, therefore applied
there, thanks Konrad!
From: Konrad Djimeli <hidden> Date: 2018-10-06 04:44:20
On 2018-10-04 19:38, Björn Töpel wrote:
Den tors 4 okt. 2018 kl 19:03 skrev Konrad Djimeli [off-list ref]:
quoted
Fix a simple typo: Completetion -> Completion
Signed-off-by: Konrad Djimeli <redacted>
---
Changes in v2:
- Update line below to be same length as text above
Documentation/networking/af_xdp.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
@@ -159,8 +159,8 @@ log2(2048) LSB of the addr will be masked off, meaning that 2048, 2050 and 3000 refers to the same chunk.-UMEM Completetion Ring-~~~~~~~~~~~~~~~~~~~~~~+UMEM Completion Ring+~~~~~~~~~~~~~~~~~~~~ The Completion Ring is used transfer ownership of UMEM frames from kernel-space to user-space. Just like the Fill ring, UMEM indicies are--
2.17.1
Thanks Konrad! For future patches, you should tag your patch with
'bpf' or 'bpf-next' as pointed out in
Documentation/bpf/bpf_devel_QA.rst. I guess this should go to 'bpf'.
Acked-by: Björn Töpel <redacted>
Thanks a lot, I would keep that in mind for future contributions.