Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: John Garry <john.g.garry@oracle.com>,
	James.Bottomley@HansenPartnership.com,
	martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, hch@lst.de,
	John Garry <john.garry@linux.dev>
Subject: Re: [RFC PATCH] scsi: core: Drop Scsi_Host.default_lock
Date: Tue, 4 Aug 2026 13:08:19 -0700	[thread overview]
Message-ID: <9a4ed570-5b19-44ca-9d22-41ab37d21014@acm.org> (raw)
In-Reply-To: <7ab3dca8-83f3-4ec7-8bb4-e9c3508a5c59@oracle.com>

On 8/4/26 12:42 PM, John Garry wrote:
> Cool, I'll go through this. But how does it handle the arm v3-related 
> drivers, like fas216? At a glance, the script requires gnu- 
> a/10.3-2021.07/binrel/gcc-arm-10.3-2021.07 - but I thought that HW like 
> this requires an even earlier toolchain version.
Correct. I think that gcc-8 or older is required to generate correct
code. But generating correct code is not required to do build testing.
Hence the following hack in my script for 32-bit ARM architectures that
deletes a GCC version check from a Kconfig file:

     if [ "${arch%-*}" = "arm" ]; then
	# gcc-9 and later do not support armv3m. Hence the sed commands below.
	local f
	for f in arch/arm/Kconfig arch/arm/mach-rpc/Kconfig; do
	    if [ -e "$f" ]; then
		sed -i 's/GCC_VERSION < 90100 && //' "$f"
	    fi
	done
	sed -i 's/select CPU_32v3/select CPU_32v4/' arch/arm/mm/Kconfig
     fi

Bart.

  reply	other threads:[~2026-08-04 20:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 11:34 [RFC PATCH] scsi: core: Drop Scsi_Host.default_lock John Garry
2026-08-04 17:53 ` Bart Van Assche
2026-08-04 19:42   ` John Garry
2026-08-04 20:08     ` Bart Van Assche [this message]
2026-08-05 13:45       ` John Garry
2026-08-05 21:47         ` Bart Van Assche
2026-08-05 22:04           ` Arnd Bergmann
2026-08-06  0:35         ` Finn Thain
2026-08-08  1:53           ` Michael Schmitz

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=9a4ed570-5b19-44ca-9d22-41ab37d21014@acm.org \
    --to=bvanassche@acm.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=hch@lst.de \
    --cc=john.g.garry@oracle.com \
    --cc=john.garry@linux.dev \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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