public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Magnus Lindholm <linmag7@gmail.com>,
	Thomas Bogendoerfer <tbogendoerfer@suse.de>,
	Christoph Hellwig <hch@infradead.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org
Subject: Re: qla1280 driver for qlogic-1040 on alpha
Date: Sun, 3 Nov 2024 23:41:40 -0800	[thread overview]
Message-ID: <Zyh6tP-eWlABiBG7@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2410311656400.40463@angie.orcam.me.uk>

On Thu, Oct 31, 2024 at 05:30:31PM +0000, Maciej W. Rozycki wrote:
>  This also means that the ISP_CFG0_1040A check also added in 2.6.9 with 
> <https://lore.kernel.org/r/20040606125825.GE31063@lst.de/> will never 
> match, possibly meaning that this code wasn't actually ever verified with 
> affected 1040A hardware.  This might also explain why a later change made 
> with commit 0888f4c33128 ("[SCSI] qla1280: don't use bitfields for 
> hardware access in isp_config") went unnoticed that changed the semantics 
> of the workaround from keeping bursts unconditionally disabled with the 
> 1040A to making them enabled in the absence of NVRAM.
> 
>  NB comments for the FIFO threshold surely are suspicious too.
> 
>  Christoph can you please have a look into it?  It seems like something 
> you ought to be quite familiar with if not for the passage of time.

Somewhat surprisingly I don't remember that details of a drive by
cleanup 20 years ago :)

So whatever fixes you have based on other implementations are probably
correct.


  parent reply	other threads:[~2024-11-04  7:41 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-19 17:37 qla1280 driver for qlogic-1040 on alpha Magnus Lindholm
2024-10-25 20:00 ` Martin K. Petersen
2024-10-25 20:48   ` Magnus Lindholm
2024-10-27 23:05     ` Magnus Lindholm
2024-10-29  2:18       ` Martin K. Petersen
2024-10-29  6:51         ` Magnus Lindholm
2024-10-30  1:02         ` Maciej W. Rozycki
2024-10-30  7:52           ` Magnus Lindholm
2024-10-30  9:25             ` Thomas Bogendoerfer
2024-10-30 11:50               ` Magnus Lindholm
2024-10-31  7:37                 ` Maciej W. Rozycki
2024-10-31 10:35                   ` Magnus Lindholm
2024-10-31 17:30                     ` Maciej W. Rozycki
2024-10-31 22:19                       ` Magnus Lindholm
2024-11-01  2:36                         ` Maciej W. Rozycki
2024-11-04  7:41                       ` Christoph Hellwig [this message]
2024-11-04 20:49                         ` Magnus Lindholm
2024-11-04 21:52                           ` Maciej W. Rozycki
2024-11-05  1:40                             ` Martin K. Petersen
2024-11-05  8:34                               ` Thomas Bogendoerfer
2024-11-05 11:17                                 ` Magnus Lindholm
2024-11-05 18:16                                 ` Maciej W. Rozycki
2024-11-05 19:24                                   ` Magnus Lindholm
2024-11-12 13:52                                     ` Thomas Bogendoerfer
2024-11-15 23:39                                       ` Magnus Lindholm
2024-11-25 19:55                                         ` Maciej W. Rozycki
2024-11-26 21:33                                           ` Magnus Lindholm
2025-01-27 16:30                                             ` Magnus Lindholm
2025-04-04 21:35                                               ` Magnus Lindholm
2024-11-05 19:56                                   ` Martin K. Petersen
2024-11-05 21:06                                     ` Magnus Lindholm
2024-11-05 21:33                                     ` Thomas Bogendoerfer
2024-11-09 18:28                                       ` Magnus Lindholm
2024-11-10 15:59                                         ` Maciej W. Rozycki
2024-11-10 17:41                                           ` Magnus Lindholm
2024-11-04 21:54                         ` Maciej W. Rozycki

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=Zyh6tP-eWlABiBG7@infradead.org \
    --to=hch@infradead.org \
    --cc=linmag7@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=martin.petersen@oracle.com \
    --cc=tbogendoerfer@suse.de \
    /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