From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752737Ab1IUAup (ORCPT ); Tue, 20 Sep 2011 20:50:45 -0400 Received: from mail-qy0-f181.google.com ([209.85.216.181]:42597 "EHLO mail-qy0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750838Ab1IUAuo convert rfc822-to-8bit (ORCPT ); Tue, 20 Sep 2011 20:50:44 -0400 MIME-Version: 1.0 In-Reply-To: <1311839519.30253.16.camel@mulgrave> References: <1311826792.28583.YahooMailNeo@web31811.mail.mud.yahoo.com> <1311839519.30253.16.camel@mulgrave> Date: Tue, 20 Sep 2011 17:50:42 -0700 X-Google-Sender-Auth: n522v4pWtT3BX8yoh_9P0ESPYB8 Message-ID: Subject: Re: [PATCH] [SCSI] libsas: Allow expander T-T attachments From: Dan Williams To: James Bottomley Cc: Luben Tuikov , "linux-scsi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Mark Salyzyn Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 28, 2011 at 12:52 AM, James Bottomley wrote: > On Wed, 2011-07-27 at 21:19 -0700, Luben Tuikov wrote: >> Allow expander table-to-table attachments for >> expanders that support it. > > This is half the code to do SAS 2.0 expanders.  You seem to have > additions from the other half (self configuring expanders) see below; > does this mean you have a patch for self configuring expanders in the > works? I'd like to see that as well, but in the meantime support for the other SAS-2 fields does not block basic operation like the lack of table-to-table support does. Can we also tag this for -stable? It's akin to a pci device id update in terms of impact. Acked-by: Dan Williams From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Williams Subject: Re: [PATCH] [SCSI] libsas: Allow expander T-T attachments Date: Tue, 20 Sep 2011 17:50:42 -0700 Message-ID: References: <1311826792.28583.YahooMailNeo@web31811.mail.mud.yahoo.com> <1311839519.30253.16.camel@mulgrave> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mail-qy0-f181.google.com ([209.85.216.181]:42597 "EHLO mail-qy0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750838Ab1IUAuo convert rfc822-to-8bit (ORCPT ); Tue, 20 Sep 2011 20:50:44 -0400 In-Reply-To: <1311839519.30253.16.camel@mulgrave> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: James Bottomley Cc: Luben Tuikov , "linux-scsi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Mark Salyzyn On Thu, Jul 28, 2011 at 12:52 AM, James Bottomley wrote: > On Wed, 2011-07-27 at 21:19 -0700, Luben Tuikov wrote: >> Allow expander table-to-table attachments for >> expanders that support it. > > This is half the code to do SAS 2.0 expanders. =A0You seem to have > additions from the other half (self configuring expanders) see below; > does this mean you have a patch for self configuring expanders in the > works? I'd like to see that as well, but in the meantime support for the other SAS-2 fields does not block basic operation like the lack of table-to-table support does. Can we also tag this for -stable? It's akin to a pci device id update in terms of impact. Acked-by: Dan Williams -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html