From: Chaitra Basappa <chaitra.basappa@broadcom.com>
To: sparclinux@vger.kernel.org
Subject: RE: mpt3sas regression...
Date: Tue, 26 Jun 2018 12:17:53 +0000 [thread overview]
Message-ID: <fc8425808a51356656b6519f20d547e3@mail.gmail.com> (raw)
In-Reply-To: <20180624.134639.2035609272357314002.davem@davemloft.net>
Hi David,
Sorry for the inconvenience caused. Yes, "scsi: mpt3sas: Bug fix for big
endian systems." patch was posted to fix sparse warnings.
I missed the testing. Currently we are testing on sparc64 system and soon
I will be reposting the patch based on the findings.
Thanks,
Chaitra
-----Original Message-----
From: David Miller [mailto:davem@davemloft.net]
Sent: Sunday, June 24, 2018 10:17 AM
To: linux-scsi@vger.kernel.org
Cc: chaitra.basappa@broadcom.com; sparclinux@vger.kernel.org
Subject: mpt3sas regression...
Commit:
==========
commit cf6bf9710cabba1fe94a4349f4eb8db623c77ebc
Author: Chaitra P B <chaitra.basappa@broadcom.com>
Date: Tue Apr 24 05:28:30 2018 -0400
scsi: mpt3sas: Bug fix for big endian systems.
==========
actually breaks big-endian. This driver has been working perfectly
fine for more a decade or so on my sparc64 test systems up until this
point.
If you are just responding to sparse warnings, please do not do that.
What big-endian system did you test this change on?
Meanwhile, I'd like to ask that this change be reverted.
Thank you.
next prev parent reply other threads:[~2018-06-26 12:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 4:46 mpt3sas regression David Miller
2018-06-26 12:17 ` Chaitra Basappa [this message]
2018-06-27 14:40 ` Chaitra Basappa
2018-06-28 0:15 ` David Miller
2018-06-28 15:57 ` Chaitra Basappa
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=fc8425808a51356656b6519f20d547e3@mail.gmail.com \
--to=chaitra.basappa@broadcom.com \
--cc=sparclinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.