From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail-bn3nam01on0087.outbound.protection.outlook.com ([104.47.33.87]:45241
        "EHLO NAM01-BN3-obe.outbound.protection.outlook.com"
        rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP
        id S1754244AbcLVQER (ORCPT <rfc822;stable@vger.kernel.org>);
        Thu, 22 Dec 2016 11:04:17 -0500
From: Don Brace <don.brace@microsemi.com>
To: Greg KH <gregkh@linuxfoundation.org>
CC: John Hall <John.Hall@microsemi.com>,
        Kevin Barnett <kevin.barnett@microsemi.com>,
        Mahesh Rajashekhara <mahesh.rajashekhara@microsemi.com>,
        Bader Ali-saleh <bader.alisaleh@microsemi.com>,
        Scott Teel <scott.teel@microsemi.com>,
        Viswas G <viswas.g@microsemi.com>,
        Justin Lindley <justin.lindley@microsemi.com>,
        Scott Benesh <scott.benesh@microsemi.com>,
        "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH] aacraid: remove wildcard for series 9 controllers
Date: Thu, 22 Dec 2016 15:32:37 +0000
Message-ID: <4993A297653ECB4581FA5C3C31323D194180DE77@avsrvexchmbx1.microsemi.net>
References: <148184562208.25166.8298541279792087398.stgit@brunhilda>
 <20161216123501.GA31355@kroah.com>
In-Reply-To: <20161216123501.GA31355@kroah.com>
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

> -----Original Message-----
> From: Greg KH [mailto:gregkh@linuxfoundation.org]
> Sent: Friday, December 16, 2016 6:35 AM
> To: Don Brace
> Cc: John Hall; Kevin Barnett; Mahesh Rajashekhara; Bader Ali-saleh; Scott
> Teel; Viswas G; Justin Lindley; Scott Benesh; stable@vger.kernel.org
> Subject: Re: [PATCH] aacraid: remove wildcard for series 9 controllers
>=20
> EXTERNAL EMAIL
>=20
>=20
> On Thu, Dec 15, 2016 at 05:47:02PM -0600, Don Brace wrote:
> > From: Kevin Barnett <kevin.barnett@microsemi.com>
> >
> > The ID we want to remove from the aacraid driver will not be available =
until
> Q1 next year,
> > so no customer currently has it yet. If they are running an older kerne=
l, the
> aacraid driver
> > will support this ID but in 'sync' mode, their servers will continue to=
 boot.
> >
> > If they upgrade to a newer kernel and do not know  to configure the
> smartpqi
> > driver and the system fails to boot, they can fall back to the previous
> > kernel and configure the smartpqi driver.
> >
> > This patch is for newer kernels going forward. We need to eliminate the
> > duplication for newer kernels. If both drivers support the same ID
> > they will have to know how to rebuild their initrd with a specific driv=
er
> > order. Customers that have servers configured with both older aacraid
> devices
> > and the newer smartpqi devices will definitely have to do this. Having =
to
> > rebuild the kernel with smartpqi enabled would seem to be an easier
> > customer experience.
> >
> > The officially supported driver for this ID is smartpqi.
> >
> > This patch has been applied to 4.10/scsi-queue
>=20
> What does this line mean?
>=20
> Have you read Documentation/stable_kernel_rules.txt for how to submit
> patches to the stable tree?
>=20
> What should I do with this patch?

Sorry about the confusion. This patch has been applied to 4.10 (ae2aae24219=
8) and
I would like to have it applied to 4.9. As it is, there will be an issue in=
 4.9 where the
aacraid driver will claim smartpqi devices and fail to support it properly.

>=20
> thanks,
>=20
> greg k-h