All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
	intel-gfx@lists.freedesktop.org,
	Nick Desaulniers <ndesaulniers@google.com>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-kbuild@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH v2 2/2] drm/i915: enable W=1 warnings by default
Date: Wed, 11 Oct 2023 23:54:13 +0300	[thread overview]
Message-ID: <87wmvs3moa.fsf@intel.com> (raw)
In-Reply-To: <CAK7LNAQ1K4X6=jW1b8cyS9vs_hpn+YGzF2qw7YTFawo-bs_9gQ@mail.gmail.com>

On Wed, 11 Oct 2023, Masahiro Yamada <masahiroy@kernel.org> wrote:
> On Wed, Oct 11, 2023 at 4:29 PM Jani Nikula <jani.nikula@intel.com> wrote:
>>
>> We enable a bunch more compiler warnings than the kernel
>> defaults. However, they've drifted to become a unique set of warnings,
>> and have increasingly fallen behind from the W=1 set.
>>
>> Align with the W=1 warnings from scripts/Makefile.extrawarn for clarity,
>> by copy-pasting them with s/KBUILD_CFLAGS/subdir-ccflags-y/ to make it
>> easier to compare in the future.
>>
>> Some of the -Wextra warnings do need to be disabled, just like in
>> Makefile.extrawarn, but take care to not disable them for W=2 or W=3
>> builds, depending on the warning.
>>
>> v2: Add back some -Wextra warning disables (Nathan)
>>
>> Cc: Arnd Bergmann <arnd@arndb.de>
>> Cc: Nick Desaulniers <ndesaulniers@google.com>
>> Cc: Nathan Chancellor <nathan@kernel.org>
>> Cc: Masahiro Yamada <masahiroy@kernel.org>
>> Reviewed-by: Nathan Chancellor <nathan@kernel.org>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Reviewed-by: Masahiro Yamada <masahiroy@kernel.org>

Thanks for the reviews everyone...

...though we missed some s/KBUILD_CFLAGS/subdir-ccflags-y/ in v2. Fixed
while applying.

BR,
Jani.


-- 
Jani Nikula, Intel

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: intel-gfx@lists.freedesktop.org, linux-kbuild@vger.kernel.org,
	Arnd Bergmann <arnd@arndb.de>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH v2 2/2] drm/i915: enable W=1 warnings by default
Date: Wed, 11 Oct 2023 23:54:13 +0300	[thread overview]
Message-ID: <87wmvs3moa.fsf@intel.com> (raw)
In-Reply-To: <CAK7LNAQ1K4X6=jW1b8cyS9vs_hpn+YGzF2qw7YTFawo-bs_9gQ@mail.gmail.com>

On Wed, 11 Oct 2023, Masahiro Yamada <masahiroy@kernel.org> wrote:
> On Wed, Oct 11, 2023 at 4:29 PM Jani Nikula <jani.nikula@intel.com> wrote:
>>
>> We enable a bunch more compiler warnings than the kernel
>> defaults. However, they've drifted to become a unique set of warnings,
>> and have increasingly fallen behind from the W=1 set.
>>
>> Align with the W=1 warnings from scripts/Makefile.extrawarn for clarity,
>> by copy-pasting them with s/KBUILD_CFLAGS/subdir-ccflags-y/ to make it
>> easier to compare in the future.
>>
>> Some of the -Wextra warnings do need to be disabled, just like in
>> Makefile.extrawarn, but take care to not disable them for W=2 or W=3
>> builds, depending on the warning.
>>
>> v2: Add back some -Wextra warning disables (Nathan)
>>
>> Cc: Arnd Bergmann <arnd@arndb.de>
>> Cc: Nick Desaulniers <ndesaulniers@google.com>
>> Cc: Nathan Chancellor <nathan@kernel.org>
>> Cc: Masahiro Yamada <masahiroy@kernel.org>
>> Reviewed-by: Nathan Chancellor <nathan@kernel.org>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Reviewed-by: Masahiro Yamada <masahiroy@kernel.org>

Thanks for the reviews everyone...

...though we missed some s/KBUILD_CFLAGS/subdir-ccflags-y/ in v2. Fixed
while applying.

BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2023-10-11 20:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11  7:29 [Intel-gfx] [PATCH v2 0/2] drm/i915: align with W=1 warnings Jani Nikula
2023-10-11  7:29 ` Jani Nikula
2023-10-11  7:29 ` [Intel-gfx] [PATCH v2 1/2] drm/i915: drop -Wall and related disables from cflags as redundant Jani Nikula
2023-10-11  7:29   ` Jani Nikula
2023-10-11 14:36   ` [Intel-gfx] " Masahiro Yamada
2023-10-11 14:36     ` Masahiro Yamada
2023-10-11  7:29 ` [Intel-gfx] [PATCH v2 2/2] drm/i915: enable W=1 warnings by default Jani Nikula
2023-10-11  7:29   ` Jani Nikula
2023-10-11 14:37   ` [Intel-gfx] " Masahiro Yamada
2023-10-11 14:37     ` Masahiro Yamada
2023-10-11 20:54     ` Jani Nikula [this message]
2023-10-11 20:54       ` Jani Nikula
2023-10-11  8:17 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: align with W=1 warnings (rev3) Patchwork
2023-10-11  8:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-11 20:13 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork

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=87wmvs3moa.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=arnd@arndb.de \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.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 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.