From: Lee Jones <lee.jones@linaro.org>
To: Federico Vaga <federico.vaga@vaga.pv.it>
Cc: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, clang-built-linux@googlegroups.com
Subject: Re: [PATCH 1/1] doc:it_IT: process: coding-style.rst: Correct __maybe_unused compiler label
Date: Thu, 23 Jul 2020 11:33:33 +0100 [thread overview]
Message-ID: <20200723103333.GO3533@dell> (raw)
In-Reply-To: <4e50d1ee2ebd55f8f87fcd5c631e97f3@vaga.pv.it>
On Thu, 16 Jul 2020, Federico Vaga wrote:
> Of course, you are right! Thanks
>
> On 2020-07-15 14:23, Lee Jones wrote:
> > Flag is __maybe_unused, not __maybe_used.
> >
> > Cc: Federico Vaga <federico.vaga@vaga.pv.it>
> > Cc: Jonathan Corbet <corbet@lwn.net>
> > Cc: linux-doc@vger.kernel.org
> > Cc: clang-built-linux@googlegroups.com
> > Signed-off-by: Lee Jones <lee.jones@linaro.org>
Any idea who will/should take this?
> > ---
> > Documentation/translations/it_IT/process/coding-style.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/translations/it_IT/process/coding-style.rst
> > b/Documentation/translations/it_IT/process/coding-style.rst
> > index 6f4f85832deea..a346f1f2ce21f 100644
> > --- a/Documentation/translations/it_IT/process/coding-style.rst
> > +++ b/Documentation/translations/it_IT/process/coding-style.rst
> > @@ -1097,7 +1097,7 @@ la direttiva condizionale su di esse.
> >
> > Se avete una variabile o funzione che potrebbe non essere usata in
> > alcune
> > configurazioni, e quindi il compilatore potrebbe avvisarvi circa la
> > definizione
> > -inutilizzata, marcate questa definizione come __maybe_used piuttosto
> > che
> > +inutilizzata, marcate questa definizione come __maybe_unused piuttosto
> > che
> > racchiuderla in una direttiva condizionale del preprocessore.
> > (Comunque,
> > se una variabile o funzione è *sempre* inutilizzata, rimuovetela).
>
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2020-07-23 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 12:23 [PATCH 1/1] doc:it_IT: process: coding-style.rst: Correct __maybe_unused compiler label Lee Jones
2020-07-16 15:00 ` Federico Vaga
2020-07-23 10:33 ` Lee Jones [this message]
2020-07-23 13:15 ` Jonathan Corbet
2020-07-23 20:43 ` Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200723103333.GO3533@dell \
--to=lee.jones@linaro.org \
--cc=clang-built-linux@googlegroups.com \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.