public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Himanshu Madhani <hmadhani@marvell.com>, Daniel Wagner <dwagner@suse.de>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
	"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Quinn Tran <qutran@marvell.com>, Martin Wilck <mwilck@suse.com>,
	Roman Bolshakov <r.bolshakov@yadro.com>
Subject: Re: [PATCH 3/4] qla2xxx: Fix endianness annotations in source files
Date: Tue, 3 Mar 2020 21:16:32 -0800	[thread overview]
Message-ID: <73d765c7-4aa5-8dd5-2254-4f2fbcafb294@acm.org> (raw)
In-Reply-To: <A9F44BB4-8DEF-48FC-BACF-B4AC2A493A54@marvell.com>

On 2020-03-03 06:10, Himanshu Madhani wrote:
> On 3/3/20, 12:36 AM, "linux-scsi-owner@vger.kernel.org on behalf of Bart Van Assche" <linux-scsi-owner@vger.kernel.org on behalf of bvanassche@acm.org> wrote:
>     On 2020-03-02 10:40, Daniel Wagner wrote:
>     > Isn't this assuming the host runs in little endian mode? Because later down...
>     
>     My goal was not to change the behavior of the code on x86. Bugs on big
>     endian systems can be fixed later on (my guess is that this driver does
>     not work reliably on big endian), and searching through the code for
>     __force casts probably provides some good starting points.
>     
> We had made sure driver works on big endian system and the reason these were not changed was to make sure it does not break big endian architecture.  It's been a few years since I verified big endian compatibility with the driver, but I am hesitant to go change things without making sure it works on big endian systems. We are taking big risk of blindly changing things. 
> 
> I'll ask our testing folks to test this out and see if we discover issue with these changes. Until then I'll hold off on Accepting changes.

Thanks Himanshu for having offered to test this series. Please use v2 of
this series as the basis for any tests.

Bart.


  reply	other threads:[~2020-03-04  5:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-02  3:30 [PATCH 0/4] Fix qla2xxx endianness annotations Bart Van Assche
2020-03-02  3:30 ` [PATCH 1/4] qla2xxx: Use raw_smp_processor_id() where appropriate Bart Van Assche
2020-03-02 16:22   ` Daniel Wagner
2020-03-02  3:30 ` [PATCH 2/4] qla2xxx: Fix endianness annotations in header files Bart Van Assche
2020-03-02 16:50   ` Daniel Wagner
2020-03-02  3:30 ` [PATCH 3/4] qla2xxx: Fix endianness annotations in source files Bart Van Assche
2020-03-02 18:40   ` Daniel Wagner
2020-03-03  6:36     ` Bart Van Assche
2020-03-03  9:24       ` Daniel Wagner
2020-03-03 14:10       ` Himanshu Madhani
2020-03-04  5:16         ` Bart Van Assche [this message]
2020-03-02  3:30 ` [PATCH 4/4] qla2xxx: Fix the code that reads from mailbox registers Bart Van Assche
2020-03-02 18:43   ` Daniel Wagner
2020-03-03  6:37     ` Bart Van Assche
2020-03-03  8:31       ` Daniel Wagner

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=73d765c7-4aa5-8dd5-2254-4f2fbcafb294@acm.org \
    --to=bvanassche@acm.org \
    --cc=dwagner@suse.de \
    --cc=hmadhani@marvell.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mwilck@suse.com \
    --cc=qutran@marvell.com \
    --cc=r.bolshakov@yadro.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