On Thu, Dec 15, 2016 at 05:47:02PM -0600, Don Brace wrote: > From: Kevin Barnett <kevin.barnett@xxxxxxxxxxxxx> > > 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 kernel, 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 driver > 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 What does this line mean? Have you read Documentation/stable_kernel_rules.txt for how to submit patches to the stable tree? What should I do with this patch? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html