Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Mirsad Todorovac <mtodorovac69@gmail.com>
To: Bart Van Assche <bvanassche@acm.org>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Nilesh Javali <njavali@marvell.com>,
	GR-QLogic-Storage-Upstream@marvell.com,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v1 1/1] scsi: gla2xxx: use flexible array member at the end of structures
Date: Sat, 26 Oct 2024 09:56:49 +0200	[thread overview]
Message-ID: <08cf23fc-a062-418b-aa90-59bc6077f281@gmail.com> (raw)
In-Reply-To: <dfd36022-2397-486c-8499-454d31072a30@acm.org>

On 10/24/24 18:55, Bart Van Assche wrote:
> On 10/23/24 9:22 PM, Mirsad Todorovac wrote:
>>  From next-20241023, it seems to have passed compilation:
>>
>>    INSTALL debian/linux-libc-dev/usr/include
>> dpkg-deb: building package 'linux-image-6.12.0-rc4-next-20241023-00001-gdcf82889780d' in '../linux-image-6.12.0-rc4-next-20241023-00001-gdcf82889780d_6.12.0-rc4-00001-gdcf82889780d-4_amd64.deb'.
>> dpkg-deb: building package 'linux-libc-dev' in '../linux-libc-dev_6.12.0-rc4-00001-gdcf82889780d-4_amd64.deb'.
>>   dpkg-genbuildinfo --build=binary -O../linux-upstream_6.12.0-rc4-00001-gdcf82889780d-4_amd64.buildinfo
>>   dpkg-genchanges --build=binary -O../linux-upstream_6.12.0-rc4-00001-gdcf82889780d-4_amd64.changes
>> dpkg-genchanges: info: binary-only upload (no source code included)
>>   dpkg-source --after-build .
>> dpkg-buildpackage: info: binary-only upload (no source included)
> 
> What kernel config is used during that kernel build? Is the qla2xxx
> driver enabled in that kernel config?
> 
> BTW, there is a typo in the subject of your email: gla2xxx should be
> qla2xxx.

You are correct. What a blunder.

> Bart.

Hi,

You were right, of course. There is no config SCSI_QLA_FC nor TCM_QLA2XXX in my .config.

$ grep config drivers/scsi/qla2xxx/Kconfig
config SCSI_QLA_FC
config TCM_QLA2XXX
config TCM_QLA2XXX_DEBUG
$ grep -E '(SCSI_QLA_FC|TCM_QLA2XXX)' .config
$ 

From what kernel robot produced, it is obvious that this should be done by something with deeper
knowledge of the driver's implementation.

Even when decreasing all those BUG_BUILD_ON() checks would be trivial, there are obviously more
gotchas.

Maybe "make allyesconfig" would spare me from such stupid errors.

But they say that a fail that makes you humble is better than a success that makes you arrogant :-/

Best regards,
Mirsad



  reply	other threads:[~2024-10-26  7:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23 22:17 [PATCH v1 1/1] scsi: gla2xxx: use flexible array member at the end of structures Mirsad Todorovac
2024-10-23 22:25 ` Bart Van Assche
2024-10-24  4:22   ` Mirsad Todorovac
2024-10-24 16:55     ` Bart Van Assche
2024-10-26  7:56       ` Mirsad Todorovac [this message]
2024-10-24 20:03 ` kernel test robot
2024-10-25 10:57 ` kernel test robot

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=08cf23fc-a062-418b-aa90-59bc6077f281@gmail.com \
    --to=mtodorovac69@gmail.com \
    --cc=GR-QLogic-Storage-Upstream@marvell.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bvanassche@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=njavali@marvell.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