From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: "James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Finn Thain <fthain@linux-m68k.org>,
Michael Schmitz <schmitzmic@gmail.com>
Subject: [PATCH 0/4] scsi: Prevent several section mismatch warnings
Date: Fri, 29 Mar 2024 22:11:40 +0100 [thread overview]
Message-ID: <cover.1711746359.git.u.kleine-koenig@pengutronix.de> (raw)
Hello,
this series fixes the same issue in four drivers. The warning is a false
positive and to suppress it the driver structs are marked with
__refdata and a comment is added to describe the (non-trivial)
situation.
Best regards
Uwe
Uwe Kleine-König (4):
scsi: a3000: Mark driver struct with __refdata to prevent section mismatch
scsi: a4000t: Mark driver struct with __refdata to prevent section mismatch
scsi: atari_scsi: Mark driver struct with __refdata to prevent section mismatch
scsi: mac_scsi: Mark driver struct with __refdata to prevent section mismatch
drivers/scsi/a3000.c | 8 +++++++-
drivers/scsi/a4000t.c | 8 +++++++-
drivers/scsi/atari_scsi.c | 8 +++++++-
drivers/scsi/mac_scsi.c | 8 +++++++-
4 files changed, 28 insertions(+), 4 deletions(-)
base-commit: a6bd6c9333397f5a0e2667d4d82fef8c970108f2
--
2.43.0
next reply other threads:[~2024-03-29 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 21:11 Uwe Kleine-König [this message]
2024-03-29 21:11 ` [PATCH 1/4] scsi: a3000: Mark driver struct with __refdata to prevent section mismatch Uwe Kleine-König
2024-03-29 21:11 ` [PATCH 2/4] scsi: a4000t: " Uwe Kleine-König
2024-03-29 21:11 ` [PATCH 3/4] scsi: atari_scsi: " Uwe Kleine-König
2024-03-29 21:11 ` [PATCH 4/4] scsi: mac_scsi: " Uwe Kleine-König
2024-04-06 1:12 ` [PATCH 0/4] scsi: Prevent several section mismatch warnings Martin K. Petersen
2024-04-09 3:08 ` Martin K. Petersen
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=cover.1711746359.git.u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=fthain@linux-m68k.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=schmitzmic@gmail.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
all inboxes | Powered by JetHome®