From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sathya Prakash <sathya.prakash@broadcom.com>,
Chaitra P B <chaitra.basappa@broadcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
Sreekanth Reddy <Sreekanth.Reddy@broadcom.com>,
Hannes Reinecke <hare@suse.de>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] Revert "scsi: mpt3sas: Fix secure erase premature termination"
Date: Sun, 15 Jan 2017 08:11:05 -0800 [thread overview]
Message-ID: <1484496665.2405.2.camel@HansenPartnership.com> (raw)
In-Reply-To: <20170115091925.GA26656@gmail.com>
On Sun, 2017-01-15 at 10:19 +0100, Ingo Molnar wrote:
> So there's a new mpt3sas SCSI driver boot regression, introduced in
> this merge window, which made one of my servers unbootable.
We're not reverting a fix that would cause regressions for others.
However, The fix was manifestly wrong, so does this fix of the fix
work for you:
http://marc.info/?l=linux-scsi&m=148329237807604
It's been languishing a bit because no-one seemed to care enough to
test or review it. IOf you can add a tested by, that will give the two
we need to push it.
James
next prev parent reply other threads:[~2017-01-15 16:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 15:02 [GIT PULL] SCSI fixes for 4.10-rc3 James Bottomley
2017-01-15 9:19 ` [PATCH] Revert "scsi: mpt3sas: Fix secure erase premature termination" Ingo Molnar
2017-01-15 16:11 ` James Bottomley [this message]
2017-01-15 18:54 ` Linus Torvalds
2017-01-15 19:13 ` James Bottomley
2017-01-15 19:41 ` Linus Torvalds
2017-01-15 19:49 ` James Bottomley
2017-01-15 22:02 ` Bart Van Assche
2017-01-16 15:27 ` Christoph Hellwig
2017-01-16 16:14 ` James Bottomley
2017-01-16 18:04 ` Christoph Hellwig
2017-01-16 9:22 ` Ingo Molnar
2017-01-16 14:24 ` James Bottomley
2017-01-16 16:30 ` Ingo Molnar
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=1484496665.2405.2.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=Sreekanth.Reddy@broadcom.com \
--cc=akpm@linux-foundation.org \
--cc=chaitra.basappa@broadcom.com \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sathya.prakash@broadcom.com \
--cc=suganath-prabu.subramani@broadcom.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.