From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Sreekanth Reddy <sreekanth.reddy@avagotech.com>,
Calvin Owens <calvinowens@fb.com>,
"Nicholas A. Bellinger" <nab@daterainc.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
"MPT-FusionLinux.pdl" <MPT-FusionLinux.pdl@avagotech.com>,
kernel-team@fb.com
Subject: Re: [PATCH 0/2] mpt3sas: Reference counting fixes from in-flight mpt2sas
Date: Fri, 28 Aug 2015 13:25:38 -0700 [thread overview]
Message-ID: <1440793538.2202.55.camel@HansenPartnership.com> (raw)
In-Reply-To: <1440702941.24282.2.camel@haakon3.risingtidesystems.com>
On Thu, 2015-08-27 at 12:15 -0700, Nicholas A. Bellinger wrote:
> On Thu, 2015-08-27 at 07:40 -0700, James Bottomley wrote:
> > On Thu, 2015-08-27 at 10:37 +0530, Sreekanth Reddy wrote:
> > > HI Nicholas & Calvin,
> > >
> > > Thanks for the patchset. Sure We will review and we do some unit
> > > testing on this patch series. Currently my bandwidth is occupied with
> > > some internal activity, so by end of next week I will acknowledge this
> > > series if all the thing are fine with this patch series.
> >
> > Calvin responded to your review feedback and that series has been
> > outstanding for a while, so I'm not going to drop it from the misc tree.
> > However, I will reorder to make it ready for the second push. You have
> > until Friday week to find a problem with it.
> >
>
> James, as mentioned this series is functionally identical to Calvin's
> mpt2sas series.
>
> Please consider merging it to scsi.git/for-next, so both series are
> together and in-sync.
Unfortunately, the driver isn't, thanks to drift between v2 and v3 of
the mpt_sas code bases. This patch is also dangerous: the early
versions left unremoved objects lying around, so getting some stress
testing from avago is very useful. At this point in the cycle, the risk
vs reward of doing a blind upport to mpt3_sas is just too great and the
time for review and stress testing too limited within the merge window.
James
next prev parent reply other threads:[~2015-08-28 20:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 4:09 [PATCH 0/2] mpt3sas: Reference counting fixes from in-flight mpt2sas Nicholas A. Bellinger
2015-08-26 4:09 ` [PATCH 1/2] mpt3sas: Refcount sas_device objects and fix unsafe list usage Nicholas A. Bellinger
2015-08-27 2:20 ` Calvin Owens
2015-08-26 4:09 ` [PATCH 2/2] mpt3sas: Refcount fw_events " Nicholas A. Bellinger
2015-08-27 2:06 ` Calvin Owens
2015-08-26 23:54 ` [PATCH 0/2] mpt3sas: Reference counting fixes from in-flight mpt2sas Calvin Owens
2015-08-26 23:58 ` Nicholas A. Bellinger
2015-08-27 5:07 ` Sreekanth Reddy
2015-08-27 7:07 ` Nicholas A. Bellinger
2015-08-27 14:40 ` James Bottomley
2015-08-27 14:48 ` Sreekanth Reddy
2015-08-27 19:15 ` Nicholas A. Bellinger
2015-08-28 20:25 ` James Bottomley [this message]
2015-08-30 7:22 ` Nicholas A. Bellinger
2015-08-30 16:14 ` James Bottomley
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=1440793538.2202.55.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=MPT-FusionLinux.pdl@avagotech.com \
--cc=calvinowens@fb.com \
--cc=hch@infradead.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@daterainc.com \
--cc=nab@linux-iscsi.org \
--cc=sreekanth.reddy@avagotech.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;
as well as URLs for NNTP newsgroup(s).