public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: HighPoint Linux Team <linux@highpoint-tech.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	James.Bottomley@HansenPartnership.com, stable@kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: [stable] [PATCH][SCSI] hptiop: add more PCI device IDs
Date: Thu, 31 Jul 2008 09:50:50 -0700	[thread overview]
Message-ID: <20080731165050.GC10422@kroah.com> (raw)
In-Reply-To: <488ECC3D.9010502@highpoint-tech.com>

On Tue, Jul 29, 2008 at 03:52:29PM +0800, HighPoint Linux Team wrote:
> At 2008/7/29 15:34, Andrew Morton wrote:
> > On Fri, 25 Jul 2008 13:29:24 +0800 HighPoint Linux Team <linux@highpoint-tech.com> wrote:
> >
> >   
> >> Add PCI device ID for new adapter models.
> >>
> >> Signed-off-by: HighPoint Linux Team <linux@highpoint-tech.com>
> >> ---
> >>
> >>  drivers/scsi/hptiop.c |    7 +++++++
> >>  1 file changed, 7 insertions(+)
> >>
> >> diff -purN linux-2.6.26-rc8/drivers/scsi/hptiop.c linux-2.6.26-rc8-hpt/drivers/scsi/hptiop.c
> >> --- linux-2.6.26-rc8/drivers/scsi/hptiop.c	2008-06-25 09:58:20.000000000 +0800
> >> +++ linux-2.6.26-rc8-hpt/drivers/scsi/hptiop.c	2008-07-24 15:09:50.000000000 +0800
> >> @@ -1249,6 +1249,13 @@ static struct pci_device_id hptiop_id_ta
> >>  	{ PCI_VDEVICE(TTI, 0x3522), (kernel_ulong_t)&hptiop_itl_ops },
> >>  	{ PCI_VDEVICE(TTI, 0x3410), (kernel_ulong_t)&hptiop_itl_ops },
> >>  	{ PCI_VDEVICE(TTI, 0x3540), (kernel_ulong_t)&hptiop_itl_ops },
> >> +	{ PCI_VDEVICE(TTI, 0x3530), (kernel_ulong_t)&hptiop_itl_ops },
> >> +	{ PCI_VDEVICE(TTI, 0x3560), (kernel_ulong_t)&hptiop_itl_ops },
> >> +	{ PCI_VDEVICE(TTI, 0x4322), (kernel_ulong_t)&hptiop_itl_ops },
> >> +	{ PCI_VDEVICE(TTI, 0x4210), (kernel_ulong_t)&hptiop_itl_ops },
> >> +	{ PCI_VDEVICE(TTI, 0x4211), (kernel_ulong_t)&hptiop_itl_ops },
> >> +	{ PCI_VDEVICE(TTI, 0x4310), (kernel_ulong_t)&hptiop_itl_ops },
> >> +	{ PCI_VDEVICE(TTI, 0x4311), (kernel_ulong_t)&hptiop_itl_ops },
> >>  	{ PCI_VDEVICE(TTI, 0x3120), (kernel_ulong_t)&hptiop_mv_ops },
> >>  	{ PCI_VDEVICE(TTI, 0x3122), (kernel_ulong_t)&hptiop_mv_ops },
> >>  	{ PCI_VDEVICE(TTI, 0x3020), (kernel_ulong_t)&hptiop_mv_ops },
> >>     
> >
> > I assume that this patch makes new devices work, whereas they do not
> > work correctly in unpatched kernels, yes?
> >
> > If so, then this patch should be backported into 2.6.25.x and 2.6.26.x.
> > Users of these kernels would presumably like their devices to work.
> >   
> Yes, this patch should also be backported to 2.6.25.x and 2.6.26.x.

What is the git commit id for this patch in Linus's tree?  I couldn't
find it when I last looked.

thanks,

greg k-h

  reply	other threads:[~2008-07-31 19:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25  5:29 [PATCH][SCSI] hptiop: add more PCI device IDs HighPoint Linux Team
2008-07-29  7:34 ` Andrew Morton
2008-07-29  7:52   ` HighPoint Linux Team
2008-07-31 16:50     ` Greg KH [this message]
2008-07-31 20:06       ` [stable] " Andrew Morton

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=20080731165050.GC10422@kroah.com \
    --to=greg@kroah.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@highpoint-tech.com \
    --cc=stable@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox