linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Desaulniers <ndesaulniers@google.com>
To: arnd@kernel.org
Cc: arnd@arndb.de, axboe@kernel.dk, bp@suse.de,
	eric.dumazet@gmail.com, jgross@suse.com, jiancai@google.com,
	linux-kernel@vger.kernel.org, linux@roeck-us.net,
	mpe@ellerman.id.au, peterz@infradead.org, tglx@linutronix.de,
	ying.huang@intel.com, Nathan Chancellor <nathan@kernel.org>,
	clang-built-linux@googlegroups.com
Subject: Re: [PATCH] smp: fix smp_call_function_single_async prototype
Date: Thu, 29 Apr 2021 11:17:16 -0700	[thread overview]
Message-ID: <20210429181716.2409874-1-ndesaulniers@google.com> (raw)
In-Reply-To: <20210429150940.3256656-1-arnd@kernel.org>

(replying manually to
https://lore.kernel.org/lkml/20210429150940.3256656-1-arnd@kernel.org/)

Thanks for the patch; with this applied I observe the following new warnings
though (for x86_64 defconfig; make LLVM=1 LLVM_IAS=1 -j72)

kernel/smp.c:515:19: warning: passing 8-byte aligned argument to 32-byte
aligned parameter 1 of 'csd_lock_record' may result in an unaligned pointer
access [-Walign-mismatch]
                csd_lock_record(csd);
                                ^
kernel/smp.c:516:14: warning: passing 8-byte aligned argument to 32-byte
aligned parameter 1 of 'csd_unlock' may result in an unaligned pointer access
[-Walign-mismatch]
                csd_unlock(csd);
                           ^
kernel/smp.c:525:14: warning: passing 8-byte aligned argument to 32-byte
aligned parameter 1 of 'csd_unlock' may result in an unaligned pointer access
[-Walign-mismatch]
                csd_unlock(csd);
                           ^

  parent reply	other threads:[~2021-04-29 18:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 15:09 [PATCH] smp: fix smp_call_function_single_async prototype Arnd Bergmann
2021-04-29 15:54 ` Jens Axboe
2021-04-29 18:17 ` Nick Desaulniers [this message]
2021-04-29 18:24   ` Nick Desaulniers
2021-04-29 18:26     ` Arnd Bergmann
2021-04-29 18:39       ` Nick Desaulniers
2021-04-29 19:08 ` kernel test robot
2021-04-29 21:44 ` kernel test robot
2021-04-29 23:00   ` Jian Cai

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=20210429181716.2409874-1-ndesaulniers@google.com \
    --to=ndesaulniers@google.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=bp@suse.de \
    --cc=clang-built-linux@googlegroups.com \
    --cc=eric.dumazet@gmail.com \
    --cc=jgross@suse.com \
    --cc=jiancai@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mpe@ellerman.id.au \
    --cc=nathan@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).