mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Xiangliang Yu <yuxiangl@marvell.com>
Cc: Jan Kasprzak <kas@fi.muni.cz>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: mvsas: add support for Supermicro AOC-SAS2LP-MV8
Date: Mon, 28 Apr 2014 18:36:25 -0700	[thread overview]
Message-ID: <1398735385.2419.69.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D4F6368598F@SC-VEXCH4.marvell.com>

On Mon, 2014-04-28 at 18:16 -0700, Xiangliang Yu wrote:
> Hi, Jan
> I think below change may be better:
> { PCI_VDEVICE(MARVELL_EXT, 0x9485), chip_9485 },

Ben Hutchings already submitted a patch for this twice, which I cc'd you
on:

http://marc.info/?t=139277203900003

will you ack it?  PCI_VDEVICE() is a sort of take it or leave it macro.
It's not important and it will look untidy and a bit confusing having a
mix of open coding and macros, so I'd say convert all or none.

James


> > Add support for the AOC-SAS2LP-MV8 SAS-2 controller from SuperMicro.
> > This controller has subdevice id 0x9485 instead of 0x9480, and apparently
> > this simple patch is the only thing needed to make it work.
> > 
> > # lspci -vn
> > [...]
> > 03:00.0 0104: 1b4b:9485 (rev 03)
> > 	Subsystem: 1b4b:9485
> > 	Flags: bus master, fast devsel, latency 0, IRQ 24
> > 	Memory at feba0000 (64-bit, non-prefetchable) [size=128K]
> > 	Memory at febc0000 (64-bit, non-prefetchable) [size=256K]
> > 	Expansion ROM at feb90000 [disabled] [size=64K]
> > 	Capabilities: [40] Power Management version 3
> > 	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
> > 	Capabilities: [70] Express Endpoint, MSI 00
> > 	Capabilities: [100] Advanced Error Reporting
> > 	Capabilities: [140] Virtual Channel
> > 	Kernel driver in use: mvsas
> > 	Kernel modules: mvsas
> > 
> > Signed-off-by: Jan Kasprzak <kas@fi.muni.cz>
> > 
> > diff --git a/drivers/scsi/mvsas/mv_init.c b/drivers/scsi/mvsas/mv_init.c
> > index 5ff978b..eacee48 100644
> > --- a/drivers/scsi/mvsas/mv_init.c
> > +++ b/drivers/scsi/mvsas/mv_init.c
> > @@ -728,6 +728,15 @@ static struct pci_device_id mvs_pci_table[] = {
> >  		.class_mask	= 0,
> >  		.driver_data	= chip_9485,
> >  	},
> > +	{
> > +		.vendor		= PCI_VENDOR_ID_MARVELL_EXT,
> > +		.device		= 0x9485,
> > +		.subvendor	= PCI_ANY_ID,
> > +		.subdevice	= 0x9485,
> > +		.class		= 0,
> > +		.class_mask	= 0,
> > +		.driver_data	= chip_9485,
> > +	},
> >  	{ PCI_VDEVICE(OCZ, 0x1021), chip_9485}, /* OCZ RevoDrive3 */
> >  	{ PCI_VDEVICE(OCZ, 0x1022), chip_9485}, /* OCZ RevoDrive3/zDriveR4 (exact
> > model unknown) */
> >  	{ PCI_VDEVICE(OCZ, 0x1040), chip_9485}, /* OCZ RevoDrive3/zDriveR4 (exact
> > model unknown) */
> > 
> > --
> > | Jan "Yenya" Kasprzak  <kas at {fi.muni.cz - work | yenya.net - private}> |
> > | New GPG 4096R/A45477D5 - see http://www.fi.muni.cz/~kas/pgp-rollover.txt |
> > | http://www.fi.muni.cz/~kas/    Journal: http://www.fi.muni.cz/~kas/blog/
> > |
> >   There's clearly a balance between "octopus merges are fine" and "Christ,
> >   that's not an octopus, that's a Cthulhu merge".         --Linus Torvalds
> --
> 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




  reply	other threads:[~2014-04-29  1:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 14:52 Jan Kasprzak
2014-04-29  1:16 ` Xiangliang Yu
2014-04-29  1:36   ` James Bottomley [this message]
2014-04-29  2:49     ` Xiangliang Yu
2014-04-29  2:56     ` Xiangliang Yu
2014-05-16 12:06       ` Jan Kasprzak
2014-05-28 11:08         ` Christoph Hellwig
2014-05-30 12:50           ` Jan Kasprzak
2014-06-02  6:46             ` Christoph Hellwig

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=1398735385.2419.69.camel@dabdike.int.hansenpartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=kas@fi.muni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=yuxiangl@marvell.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

all inboxes | Powered by JetHome®