Documentation: kernel-hacking: Remove comma
PATCH 1/1 Documentation: kernel-hacking: Remove comma
The comma is wrong, remove it.
--- Documentation/kernel-hacking/hacking.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/kernel-hacking/hacking.rst +1 -1
@@ -49,7 +49,7 @@ User Context User context is when you are coming in from a system call or other trap: like userspace, you can be preempted by more important tasks and by -interrupts. You can sleep, by calling :c:func:`schedule()`. +interrupts. You can sleep by calling :c:func:`schedule()`. .. note::
Signature · 2 lines
Thorsten Blum <[email protected]> GPG: 1D60 735E 8AEF 3BE4 73B6 9D84 7336 78FD 8DFE EAD4
Quoted 3 lines · Thorsten Blum
The comma is wrong, remove it.
Signed-off-by Thorsten Blum <[email protected]>
Quoted 17 lines
--- Documentation/kernel-hacking/hacking.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Documentation/kernel-hacking/hacking.rst +1
-1@@ -49,7 +49,7 @@ User Context User context is when you are coming in from a system call or other trap: like userspace, you can be preempted by more important tasks and by -interrupts. You can sleep, by calling :c:func:`schedule()`. +interrupts. You can sleep by calling :c:func:`schedule()`. .. note::
Signature · 1 line
~Randy
Jonathan Corbet
maintainerQuoted 12 lines · Thorsten Blum
The comma is wrong, remove it.
Signed-off-by Thorsten Blum <[email protected]>--- Documentation/kernel-hacking/hacking.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Documentation/kernel-hacking/hacking.rst +0
-0
Documentation/kernel-hacking/hacking.rst User Context · line 52
Quoted 5 lines
Documentation/kernel-hacking/hacking.rst +1
-1@@ -49,7 +49,7 @@ User Context User context is when you are coming in from a system call or other trap: like userspace, you can be preempted by more important tasks and by -interrupts. You can sleep, by calling :c:func:`schedule()`. +interrupts. You can sleep by calling :c:func:`schedule()`.
That's a fine change, but can I prevail upon you to get rid of the usless :c:func: annotation while you're playing with that line?
Thanks,
jon
Quoted 14 lines · Jonathan Corbet
Quoted 13 lines · Thorsten Blum
The comma is wrong, remove it.
Signed-off-by Thorsten Blum <[email protected]>---
Documentation/kernel-hacking/hacking.rst| 2 +-1 file changed, 1 insertion(+), 1 deletion(-)Documentation/kernel-hacking/hacking.rst +0
-0@@ -49,7 +49,7 @@ User Context
Quoted 7 lines
Documentation/kernel-hacking/hacking.rst User Context · line 52
Quoted 4 lines
User context is when you are coming in from a system call or other trap:
like userspace, you can be preempted by more important tasks and byDocumentation/kernel-hacking/hacking.rst +1
-1-interrupts. You can sleep, by calling :c:func:`schedule()`. +interrupts. You can sleep by calling :c:func:`schedule()`.That's a fine change, but can I prevail upon you to get rid of the usless :c:func: annotation while you're playing with that line?
So just schedule()?
:c:func: is used very often in the same file - maybe we should remove them all in a separate patch? I'm fine either way.
Thanks,
Thorsten
Jonathan Corbet
maintainerQuoted 4 lines · Thorsten Blum
Quoted 2 lines
That's a fine change, but can I prevail upon you to get rid of the usless :c:func: annotation while you're playing with that line?
So just
schedule()?
Yes. We should never use :c:func:, our automarkup code will do the right thing in its absence.
Quoted 2 lines
:c:func: is used very often in the same file - maybe we should remove them all in a separate patch? I'm fine either way.
If you want to do them all, a separate patch probably makes sense. That would be wonderful.
Thanks,
jon
Quoted 12 lines · Thorsten Blum
The comma is wrong, remove it.
Signed-off-by Thorsten Blum <[email protected]>--- Documentation/kernel-hacking/hacking.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Documentation/kernel-hacking/hacking.rst +0
-0
Documentation/kernel-hacking/hacking.rst User Context · line 53
Quoted 6 lines
Documentation/kernel-hacking/hacking.rst +1
-1@@ -49,7 +49,7 @@ User Context User context is when you are coming in from a system call or other trap: like userspace, you can be preempted by more important tasks and by -interrupts. You can sleep, by calling :c:func:`schedule()`. +interrupts. You can sleep by calling :c:func:`schedule()`.
Applied, thanks,
jon