* [PATCH] docs: Fix function name trailing double-()s
@ 2020-08-08 6:49 Kees Cook
2020-08-08 15:15 ` Paul E. McKenney
2020-08-11 16:48 ` Jonathan Corbet
0 siblings, 2 replies; 4+ messages in thread
From: Kees Cook @ 2020-08-08 6:49 UTC (permalink / raw)
To: Jonathan Corbet; +Cc: linux-kernel, linux-doc, Paul E. McKenney
I noticed a double-() after a function name in deprecated.rst today. Fix
that one and two others in the Documentation/ tree.
Signed-off-by: Kees Cook <keescook@chromium.org>
---
Documentation/RCU/lockdep.rst | 2 +-
Documentation/process/deprecated.rst | 2 +-
Documentation/translations/it_IT/process/deprecated.rst | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/RCU/lockdep.rst b/Documentation/RCU/lockdep.rst
index f1fc8ae3846a..cc860a0c296b 100644
--- a/Documentation/RCU/lockdep.rst
+++ b/Documentation/RCU/lockdep.rst
@@ -49,7 +49,7 @@ checking of rcu_dereference() primitives:
is invoked by both RCU-sched readers and updaters.
srcu_dereference_check(p, c):
Use explicit check expression "c" along with
- srcu_read_lock_held()(). This is useful in code that
+ srcu_read_lock_held(). This is useful in code that
is invoked by both SRCU readers and updaters.
rcu_dereference_raw(p):
Don't check. (Use sparingly, if at all.)
diff --git a/Documentation/process/deprecated.rst b/Documentation/process/deprecated.rst
index 4a9aa4f0681e..918e32d76fc4 100644
--- a/Documentation/process/deprecated.rst
+++ b/Documentation/process/deprecated.rst
@@ -142,7 +142,7 @@ only NUL-terminated strings. The safe replacement is strscpy().
(Users of strscpy() still needing NUL-padding should instead
use strscpy_pad().)
-If a caller is using non-NUL-terminated strings, strncpy()() can
+If a caller is using non-NUL-terminated strings, strncpy() can
still be used, but destinations should be marked with the `__nonstring
<https://gcc.gnu.org/onlinedocs/gcc/Common-Variable-Attributes.html>`_
attribute to avoid future compiler warnings.
diff --git a/Documentation/translations/it_IT/process/deprecated.rst b/Documentation/translations/it_IT/process/deprecated.rst
index e108eaf82cf6..a642ff3fdc8b 100644
--- a/Documentation/translations/it_IT/process/deprecated.rst
+++ b/Documentation/translations/it_IT/process/deprecated.rst
@@ -130,7 +130,7 @@ chi usa solo stringe terminate. La versione sicura da usare è
strscpy(). (chi usa strscpy() e necessita di estendere la
terminazione con NUL deve aggiungere una chiamata a memset())
-Se il chiamate no usa stringhe terminate con NUL, allore strncpy()()
+Se il chiamate no usa stringhe terminate con NUL, allore strncpy()
può continuare ad essere usata, ma i buffer di destinazione devono essere
marchiati con l'attributo `__nonstring <https://gcc.gnu.org/onlinedocs/gcc/Common-Variable-Attributes.html>`_
per evitare avvisi durante la compilazione.
--
2.25.1
--
Kees Cook
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH] docs: Fix function name trailing double-()s
2020-08-08 6:49 [PATCH] docs: Fix function name trailing double-()s Kees Cook
@ 2020-08-08 15:15 ` Paul E. McKenney
2020-08-11 16:48 ` Jonathan Corbet
1 sibling, 0 replies; 4+ messages in thread
From: Paul E. McKenney @ 2020-08-08 15:15 UTC (permalink / raw)
To: Kees Cook; +Cc: Jonathan Corbet, linux-kernel, linux-doc
On Fri, Aug 07, 2020 at 11:49:59PM -0700, Kees Cook wrote:
> I noticed a double-() after a function name in deprecated.rst today. Fix
> that one and two others in the Documentation/ tree.
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
For the RCU hunk:
Acked-by: Paul E. McKenney <paulmck@kernel.org>
Or I could take the Documentation/RCU/lockdep.rst portion, if you
would prefer.
> ---
> Documentation/RCU/lockdep.rst | 2 +-
> Documentation/process/deprecated.rst | 2 +-
> Documentation/translations/it_IT/process/deprecated.rst | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/RCU/lockdep.rst b/Documentation/RCU/lockdep.rst
> index f1fc8ae3846a..cc860a0c296b 100644
> --- a/Documentation/RCU/lockdep.rst
> +++ b/Documentation/RCU/lockdep.rst
> @@ -49,7 +49,7 @@ checking of rcu_dereference() primitives:
> is invoked by both RCU-sched readers and updaters.
> srcu_dereference_check(p, c):
> Use explicit check expression "c" along with
> - srcu_read_lock_held()(). This is useful in code that
> + srcu_read_lock_held(). This is useful in code that
> is invoked by both SRCU readers and updaters.
> rcu_dereference_raw(p):
> Don't check. (Use sparingly, if at all.)
> diff --git a/Documentation/process/deprecated.rst b/Documentation/process/deprecated.rst
> index 4a9aa4f0681e..918e32d76fc4 100644
> --- a/Documentation/process/deprecated.rst
> +++ b/Documentation/process/deprecated.rst
> @@ -142,7 +142,7 @@ only NUL-terminated strings. The safe replacement is strscpy().
> (Users of strscpy() still needing NUL-padding should instead
> use strscpy_pad().)
>
> -If a caller is using non-NUL-terminated strings, strncpy()() can
> +If a caller is using non-NUL-terminated strings, strncpy() can
> still be used, but destinations should be marked with the `__nonstring
> <https://gcc.gnu.org/onlinedocs/gcc/Common-Variable-Attributes.html>`_
> attribute to avoid future compiler warnings.
> diff --git a/Documentation/translations/it_IT/process/deprecated.rst b/Documentation/translations/it_IT/process/deprecated.rst
> index e108eaf82cf6..a642ff3fdc8b 100644
> --- a/Documentation/translations/it_IT/process/deprecated.rst
> +++ b/Documentation/translations/it_IT/process/deprecated.rst
> @@ -130,7 +130,7 @@ chi usa solo stringe terminate. La versione sicura da usare è
> strscpy(). (chi usa strscpy() e necessita di estendere la
> terminazione con NUL deve aggiungere una chiamata a memset())
>
> -Se il chiamate no usa stringhe terminate con NUL, allore strncpy()()
> +Se il chiamate no usa stringhe terminate con NUL, allore strncpy()
> può continuare ad essere usata, ma i buffer di destinazione devono essere
> marchiati con l'attributo `__nonstring <https://gcc.gnu.org/onlinedocs/gcc/Common-Variable-Attributes.html>`_
> per evitare avvisi durante la compilazione.
> --
> 2.25.1
>
>
> --
> Kees Cook
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] docs: Fix function name trailing double-()s
2020-08-08 6:49 [PATCH] docs: Fix function name trailing double-()s Kees Cook
2020-08-08 15:15 ` Paul E. McKenney
@ 2020-08-11 16:48 ` Jonathan Corbet
2020-08-11 21:24 ` Kees Cook
1 sibling, 1 reply; 4+ messages in thread
From: Jonathan Corbet @ 2020-08-11 16:48 UTC (permalink / raw)
To: Kees Cook; +Cc: linux-kernel, linux-doc, Paul E. McKenney
On Fri, 7 Aug 2020 23:49:59 -0700
Kees Cook <keescook@chromium.org> wrote:
> I noticed a double-() after a function name in deprecated.rst today. Fix
> that one and two others in the Documentation/ tree.
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> Documentation/RCU/lockdep.rst | 2 +-
> Documentation/process/deprecated.rst | 2 +-
> Documentation/translations/it_IT/process/deprecated.rst | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
This one doesn't apply, and it crashes b4 outright. The problem seems to
be some sort of encoding confusion...?
Thanks,
jon
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] docs: Fix function name trailing double-()s
2020-08-11 16:48 ` Jonathan Corbet
@ 2020-08-11 21:24 ` Kees Cook
0 siblings, 0 replies; 4+ messages in thread
From: Kees Cook @ 2020-08-11 21:24 UTC (permalink / raw)
To: Jonathan Corbet; +Cc: linux-kernel, linux-doc, Paul E. McKenney
On Tue, Aug 11, 2020 at 10:48:34AM -0600, Jonathan Corbet wrote:
> On Fri, 7 Aug 2020 23:49:59 -0700
> Kees Cook <keescook@chromium.org> wrote:
>
> > I noticed a double-() after a function name in deprecated.rst today. Fix
> > that one and two others in the Documentation/ tree.
> >
> > Signed-off-by: Kees Cook <keescook@chromium.org>
> > ---
> > Documentation/RCU/lockdep.rst | 2 +-
> > Documentation/process/deprecated.rst | 2 +-
> > Documentation/translations/it_IT/process/deprecated.rst | 2 +-
> > 3 files changed, 3 insertions(+), 3 deletions(-)
>
> This one doesn't apply, and it crashes b4 outright. The problem seems to
> be some sort of encoding confusion...?
Hmmm. Weird. Something in the translation file? Let me try to re-send.
--
Kees Cook
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-08-11 21:25 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-08 6:49 [PATCH] docs: Fix function name trailing double-()s Kees Cook
2020-08-08 15:15 ` Paul E. McKenney
2020-08-11 16:48 ` Jonathan Corbet
2020-08-11 21:24 ` Kees Cook
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).