public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: "Kristleifur Daðason" <kristleifur@gmail.com>
Cc: Orion Poplawski <orion@cora.nwra.com>, linux-scsi@vger.kernel.org
Subject: Re: MVSAS status
Date: Thu, 11 Feb 2010 13:55:40 -0500	[thread overview]
Message-ID: <1265914540.13197.57.camel@mulgrave.site> (raw)
In-Reply-To: <73e903671002110150h3c4ae0dcq17625f6d9b545bf4@mail.gmail.com>

On Thu, 2010-02-11 at 09:50 +0000, Kristleifur Daðason wrote:
> On Tue, Feb 9, 2010 at 11:32 PM, Orion Poplawski <orion@cora.nwra.com> wrote:
> >
> > What's the status of the MVSAS patches posted in November '09?  I'm just trying
> > to get started with mvsas and running into the mvs_abort_task issue.  At least
> > one person has reported that stability improved, but it looks like there were
> > some other issues with the patches.  Any chance on seeing this in the mainline
> > kernel soon?  Are there updated versions?  A git tree to pull from?
> >
> 
> As far as I know, the patches from November were rejected because the
> patches themselves weren't solid enough - meaning there were some
> cross-references between each of the seven patches, things like that.
> The functionality was fine, at least a definite improvement. Ideally,
> there would have been another set of patches to top things up and
> really get everything running smoothly.

There were two reasons for the reject.  The first was that the series
just wasn't bisectable.  This is annoying but not completely fatal, and
if it were a required bug fix I can just squash all the patches together
to apply to make a single commit.  I hate doing this but I've done it
before with problem vendor patch series.

The bigger problem was there were several reports of the rate of kernel
panics increasing with this patch series applied.  If the patch series
is going to decrease stability, it's not worth applying.

I can fix the first if someone can do a solid comparison and assure me
that the patch series does actually increase not decrease stability.

> I haven't come across any patch traffic for the card after that November batch.

Yes, Marvell has gone radio silent.

> In the interests of getting these amazingly cheap and effective cards
> running properly on Linux, it would be extremely good if someone
> experienced with Linux patches would get involved in the matter with
> Mr. Andy Yan from Marvell, straighten things out, get the ball rolling
> and make the driver stick in mainline. When I emailed him, Mr. Yan was
> very helpful and sent me the patches and some info. I tried to fix the
> patches myself but was in over my head. And had no time. Etc.

OK, I'll try 1:1 email with Marvell and Andy and see what comes out.

James


--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-02-11 18:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09 23:32 MVSAS status Orion Poplawski
2010-02-10  9:22 ` Audio Haven
2010-02-10  9:36   ` Caspar Smit
2010-02-10  9:39   ` Mikael Abrahamsson
2010-02-10  9:53     ` Re[2]: " Erno Kovacs
2010-02-11  9:50 ` Kristleifur Daðason
2010-02-11 11:20   ` Mikael Abrahamsson
2010-02-11 11:21     ` Kristleifur Daðason
2010-02-11 18:30   ` Orion Poplawski
2010-02-11 18:55   ` James Bottomley [this message]
2010-02-12 12:12     ` Patch for MVSAS Srinivas Naga Venkatasatya Pasagadugula - ERS, HCL Tech
     [not found]       ` <6B62480106F2B34D8404CF2FDAA4D9EF71F637D6DB@CHN-HCLT-EVS06.HCLT.CORP.H CL.IN-99D05D88-A0F3-0C58-BFB2-2F138E38F61D>
2010-02-13  9:17         ` Caspar Smit
2010-02-14 10:00       ` Mikael Abrahamsson

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=1265914540.13197.57.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=kristleifur@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=orion@cora.nwra.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