From: Jian Cai <jiancai@google.com>
To: unlisted-recipients:; (no To-header on input)
Cc: cjdb@google.com, manojgupta@google.com, llozano@google.com,
clang-built-linux@googlegroups.com, Jian Cai <jiancai@google.com>,
Guenter Roeck <linux@roeck-us.net>, Jens Axboe <axboe@kernel.dk>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] blk-mq: fix alignment mismatch.
Date: Tue, 30 Mar 2021 16:02:49 -0700 [thread overview]
Message-ID: <20210330230249.709221-1-jiancai@google.com> (raw)
This fixes the mismatch of alignments between csd and its use as an
argument to smp_call_function_single_async, which causes build failure
when -Walign-mismatch in Clang is used.
Link:
http://crrev.com/c/1193732
Suggested-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Jian Cai <jiancai@google.com>
---
include/linux/blkdev.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
index bc6bc8383b43..3b92330d95ad 100644
--- a/include/linux/blkdev.h
+++ b/include/linux/blkdev.h
@@ -231,7 +231,7 @@ struct request {
unsigned long deadline;
union {
- struct __call_single_data csd;
+ call_single_data_t csd;
u64 fifo_time;
};
--
2.31.0.291.g576ba9dcdaf-goog
next reply other threads:[~2021-03-30 23:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 23:02 Jian Cai [this message]
2021-03-30 23:12 ` [PATCH] blk-mq: fix alignment mismatch Guenter Roeck
2021-03-30 23:29 ` Nathan Chancellor
2021-03-31 0:26 ` Guenter Roeck
2021-03-31 1:31 ` Jian Cai
2021-03-31 21:27 ` Jian Cai
2021-03-31 21:58 ` Nathan Chancellor
2021-03-31 22:06 ` Nick Desaulniers
2021-04-08 17:57 ` Jian Cai
2021-04-08 18:12 ` Nathan Chancellor
2021-04-08 18:42 ` Jian Cai
2021-04-08 19:44 ` [PATCH] block: Disable -Walign-mismatch for blk-mq.c Nathan Chancellor
2021-04-08 19:52 ` Guenter Roeck
2021-03-31 10:38 ` [PATCH] blk-mq: fix alignment mismatch David Laight
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=20210330230249.709221-1-jiancai@google.com \
--to=jiancai@google.com \
--cc=axboe@kernel.dk \
--cc=cjdb@google.com \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=llozano@google.com \
--cc=manojgupta@google.com \
--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 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).