All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
Cc: Tomas Henzl <thenzl@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"James E. J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	LKML <linux-kernel@vger.kernel.org>,
	LKML-scsi <linux-scsi@vger.kernel.org>,
	"Stephen M. Cameron" <scameron@beardog.cce.hp.com>
Subject: Re: [PATCH 1/1] scsi: hpsa, add all PCI ID's that HP has in svn
Date: Fri, 17 Jan 2014 16:31:07 +0100	[thread overview]
Message-ID: <52D94CBB.5020701@suse.de> (raw)
In-Reply-To: <48275AD710FCA34184C2B6186B4016B32D1A0B01@G6W2491.americas.hpqcorp.net>

On 01/17/2014 04:17 PM, Miller, Mike (OS Dev) wrote:
> 
> 
>> -----Original Message-----
>> From: Tomas Henzl [mailto:thenzl@redhat.com]
>> Sent: Friday, January 17, 2014 9:14 AM
>> To: Miller, Mike (OS Dev); Andrew Morton; James E. J. Bottomley
>> Cc: LKML; LKML-scsi; hare@suse.de; Stephen M. Cameron
>> Subject: Re: [PATCH 1/1] scsi: hpsa, add all PCI ID's that HP has in svn
>>
>> On 01/16/2014 08:51 PM, Mike Miller wrote:
>>> From: Mike Miller <mike.miller@hp.com>
>>>
>>> This patch has every ID we have in our svn repository. Some
>>> controllers were cancelled, others added, now the cancelled ones are
>>> back. Apparently the debate rages on about which controllers are
>>> cancelled, which are not, whatever. Please accept this patch. It is
>>> dependent upon the patches I sent yesterday.
>>> This patch made/tested against kernel-3.13.0-rc8
>>>
>>> Signed-off-by: Mike Miller <mike.miller@hp.com>
>>> ---
>>>  drivers/scsi/hpsa.c |   12 ++++++++++++
>>>  1 files changed, 12 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c index
>>> 348b207..3affec5 100644
>>> --- a/drivers/scsi/hpsa.c
>>> +++ b/drivers/scsi/hpsa.c
>>> @@ -100,6 +100,7 @@ static const struct pci_device_id
>> hpsa_pci_device_id[] = {
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSF,     0x103C,
>> 0x3354},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSF,     0x103C,
>> 0x3355},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSF,     0x103C,
>> 0x3356},
>>> +	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSH,     0x103C,
>> 0x1920},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSH,     0x103C,
>> 0x1921},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSH,     0x103C,
>> 0x1922},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSH,     0x103C,
>> 0x1923},
>>> @@ -108,15 +109,19 @@ static const struct pci_device_id
>> hpsa_pci_device_id[] = {
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSH,     0x103C,
>> 0x1926},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSH,     0x103C,
>> 0x1928},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSH,     0x103C,
>> 0x1929},
>>> +	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSH,     0x103C,
>> 0x192A},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21BD},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21BE},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21BF},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C0},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C2},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C3},
>>> +	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C4},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C5},
>>> +	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C6},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C7},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C8},
>>> +	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C9},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21CA},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21CB},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21CC},
>>> @@ -149,22 +154,29 @@ static struct board_type products[] = {
>>>  	{0x3354103C, "Smart Array P420i", &SA5_access},
>>>  	{0x3355103C, "Smart Array P220i", &SA5_access},
>>>  	{0x3356103C, "Smart Array P721m", &SA5_access},
>>> +	{0x1920103C, "Smart Array P430i", &SA5_access},
>>>  	{0x1921103C, "Smart Array P830i", &SA5_access},
>>>  	{0x1922103C, "Smart Array P430", &SA5_access},
>>>  	{0x1923103C, "Smart Array P431", &SA5_access},
>>>  	{0x1924103C, "Smart Array P830", &SA5_access},
>>> +	{0x1925103C, "Smart Array P831", &SA5_access},
>>>  	{0x1926103C, "Smart Array P731m", &SA5_access},
>>>  	{0x1928103C, "Smart Array P230i", &SA5_access},
>>>  	{0x1929103C, "Smart Array P530", &SA5_access},
>>> +	{0x192A103C, "Smart Array P531", &SA5_access},
>>>  	{0x21BD103C, "Smart Array", &SA5_access},
>>>  	{0x21BE103C, "Smart Array", &SA5_access},
>>>  	{0x21BF103C, "Smart Array", &SA5_access},
>>>  	{0x21C0103C, "Smart Array", &SA5_access},
>>> +	{0x21C1103C, "Smart Array", &SA5_access},
>>
>> I think that both tables should be in sync - but there is no 0x21c1 in
>> hpsa_pci_device_id (and the 0x1925), could you clarify that?
>>
>> Thanks, Tomas
> 
> Crap. It seems like these menial tasks get the better of me. I'll correct and resubmit.
> 
Hmm. Seeing that hpsa is now well capable of supporting even older
SmartArray controllers, is there really a point in updating the
PCI-ID list every time?
Wouldn't you be better off by just using the catch-all phrase
and remove all the individual IDs?

That way you would just have to update _one_ list ...

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
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

WARNING: multiple messages have this Message-ID (diff)
From: Hannes Reinecke <hare@suse.de>
To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
Cc: Tomas Henzl <thenzl@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"James E. J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	LKML <linux-kernel@vger.kernel.org>,
	LKML-scsi <linux-scsi@vger.kernel.org>,
	"Stephen M. Cameron" <scameron@beardog.cce.hp.com>
Subject: Re: [PATCH 1/1] scsi: hpsa, add all PCI ID's that HP has in svn
Date: Fri, 17 Jan 2014 16:31:07 +0100	[thread overview]
Message-ID: <52D94CBB.5020701@suse.de> (raw)
In-Reply-To: <48275AD710FCA34184C2B6186B4016B32D1A0B01@G6W2491.americas.hpqcorp.net>

On 01/17/2014 04:17 PM, Miller, Mike (OS Dev) wrote:
> 
> 
>> -----Original Message-----
>> From: Tomas Henzl [mailto:thenzl@redhat.com]
>> Sent: Friday, January 17, 2014 9:14 AM
>> To: Miller, Mike (OS Dev); Andrew Morton; James E. J. Bottomley
>> Cc: LKML; LKML-scsi; hare@suse.de; Stephen M. Cameron
>> Subject: Re: [PATCH 1/1] scsi: hpsa, add all PCI ID's that HP has in svn
>>
>> On 01/16/2014 08:51 PM, Mike Miller wrote:
>>> From: Mike Miller <mike.miller@hp.com>
>>>
>>> This patch has every ID we have in our svn repository. Some
>>> controllers were cancelled, others added, now the cancelled ones are
>>> back. Apparently the debate rages on about which controllers are
>>> cancelled, which are not, whatever. Please accept this patch. It is
>>> dependent upon the patches I sent yesterday.
>>> This patch made/tested against kernel-3.13.0-rc8
>>>
>>> Signed-off-by: Mike Miller <mike.miller@hp.com>
>>> ---
>>>  drivers/scsi/hpsa.c |   12 ++++++++++++
>>>  1 files changed, 12 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c index
>>> 348b207..3affec5 100644
>>> --- a/drivers/scsi/hpsa.c
>>> +++ b/drivers/scsi/hpsa.c
>>> @@ -100,6 +100,7 @@ static const struct pci_device_id
>> hpsa_pci_device_id[] = {
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSF,     0x103C,
>> 0x3354},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSF,     0x103C,
>> 0x3355},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSF,     0x103C,
>> 0x3356},
>>> +	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSH,     0x103C,
>> 0x1920},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSH,     0x103C,
>> 0x1921},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSH,     0x103C,
>> 0x1922},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSH,     0x103C,
>> 0x1923},
>>> @@ -108,15 +109,19 @@ static const struct pci_device_id
>> hpsa_pci_device_id[] = {
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSH,     0x103C,
>> 0x1926},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSH,     0x103C,
>> 0x1928},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSH,     0x103C,
>> 0x1929},
>>> +	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSH,     0x103C,
>> 0x192A},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21BD},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21BE},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21BF},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C0},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C2},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C3},
>>> +	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C4},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C5},
>>> +	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C6},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C7},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C8},
>>> +	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21C9},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21CA},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21CB},
>>>  	{PCI_VENDOR_ID_HP,     PCI_DEVICE_ID_HP_CISSI,     0x103C,
>> 0x21CC},
>>> @@ -149,22 +154,29 @@ static struct board_type products[] = {
>>>  	{0x3354103C, "Smart Array P420i", &SA5_access},
>>>  	{0x3355103C, "Smart Array P220i", &SA5_access},
>>>  	{0x3356103C, "Smart Array P721m", &SA5_access},
>>> +	{0x1920103C, "Smart Array P430i", &SA5_access},
>>>  	{0x1921103C, "Smart Array P830i", &SA5_access},
>>>  	{0x1922103C, "Smart Array P430", &SA5_access},
>>>  	{0x1923103C, "Smart Array P431", &SA5_access},
>>>  	{0x1924103C, "Smart Array P830", &SA5_access},
>>> +	{0x1925103C, "Smart Array P831", &SA5_access},
>>>  	{0x1926103C, "Smart Array P731m", &SA5_access},
>>>  	{0x1928103C, "Smart Array P230i", &SA5_access},
>>>  	{0x1929103C, "Smart Array P530", &SA5_access},
>>> +	{0x192A103C, "Smart Array P531", &SA5_access},
>>>  	{0x21BD103C, "Smart Array", &SA5_access},
>>>  	{0x21BE103C, "Smart Array", &SA5_access},
>>>  	{0x21BF103C, "Smart Array", &SA5_access},
>>>  	{0x21C0103C, "Smart Array", &SA5_access},
>>> +	{0x21C1103C, "Smart Array", &SA5_access},
>>
>> I think that both tables should be in sync - but there is no 0x21c1 in
>> hpsa_pci_device_id (and the 0x1925), could you clarify that?
>>
>> Thanks, Tomas
> 
> Crap. It seems like these menial tasks get the better of me. I'll correct and resubmit.
> 
Hmm. Seeing that hpsa is now well capable of supporting even older
SmartArray controllers, is there really a point in updating the
PCI-ID list every time?
Wouldn't you be better off by just using the catch-all phrase
and remove all the individual IDs?

That way you would just have to update _one_ list ...

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2014-01-17 15:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 19:51 [PATCH 1/1] scsi: hpsa, add all PCI ID's that HP has in svn Mike Miller
2014-01-17 15:13 ` Tomas Henzl
2014-01-17 15:17   ` Miller, Mike (OS Dev)
2014-01-17 15:31     ` Hannes Reinecke [this message]
2014-01-17 15:31       ` Hannes Reinecke
2014-01-17 15:45       ` Tomas Henzl
2014-01-17 16:01       ` Miller, Mike (OS Dev)

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=52D94CBB.5020701@suse.de \
    --to=hare@suse.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Mike.Miller@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=scameron@beardog.cce.hp.com \
    --cc=thenzl@redhat.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 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.