Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Trilok Soni <quic_tsoni@quicinc.com>
Cc: Bill Wendling <morbo@google.com>, Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	llvm@lists.linux.dev
Subject: Re: [PATCH] soc: qcom: smem: use correct format characters
Date: Wed, 16 Mar 2022 16:25:25 -0700	[thread overview]
Message-ID: <YjJx5Q0OUDRzIowG@thelio-3990X> (raw)
In-Reply-To: <15ebcddf-a84d-7293-f672-0e8ec47537e8@quicinc.com>

On Wed, Mar 16, 2022 at 04:17:06PM -0700, Trilok Soni wrote:
> On 3/16/2022 2:31 PM, Bill Wendling wrote:
> > When compiling with -Wformat, clang emits the following warnings:
> > 
> 
> I thought we have -Wno-format by default enabled for arm64, isn't it?

Yes, -Wformat is turned off for clang in the default kernel build on all
architectures (see scripts/Makefile.extrawarn). However, it can easily
be enabled with W=1 and we should eventually get this turned on for
clang like gcc so that developers who only use clang can catch instances
of it.

Cheers,
Nathan

  reply	other threads:[~2022-03-16 23:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 21:31 [PATCH] soc: qcom: smem: use correct format characters Bill Wendling
2022-03-16 23:17 ` Trilok Soni
2022-03-16 23:25   ` Nathan Chancellor [this message]
2022-03-18 18:02 ` Nathan Chancellor
2022-03-18 18:27   ` Bill Wendling
2022-03-21 15:24     ` Bjorn Andersson
2022-03-21 17:50       ` Bill Wendling
2022-03-21 17:49 ` Bill Wendling
2022-06-03 21:03   ` Justin Stitt
2022-07-01 22:05     ` Nick Desaulniers
2022-07-04 12:28       ` Arnd Bergmann

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=YjJx5Q0OUDRzIowG@thelio-3990X \
    --to=nathan@kernel.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=ndesaulniers@google.com \
    --cc=quic_tsoni@quicinc.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox