[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a3fvRQ+oUg=EUuWxdyyyMGHiL7sQMLhCY53sfCRyinOAA@mail.gmail.com>
Date: Fri, 3 Nov 2017 11:19:50 +0100
From: Arnd Bergmann <arnd@...db.de>
To: John Garry <john.garry@...wei.com>
Cc: "James E.J. Bottomley" <jejb@...ux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Xiang Chen <chenxiang66@...ilicon.com>,
linux-scsi <linux-scsi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linuxarm <linuxarm@...wei.com>,
Shiju Jose <shiju.jose@...wei.com>
Subject: Re: [PATCH] scsi: hisi_sas: select CONFIG_RAS
On Fri, Nov 3, 2017 at 11:14 AM, John Garry <john.garry@...wei.com> wrote:
> + Shiju, who authored the original patch
>
>> index d42f29a5eb65..6ad8a6251d21 100644
>> --- a/drivers/scsi/hisi_sas/Kconfig
>> +++ b/drivers/scsi/hisi_sas/Kconfig
>> @@ -4,6 +4,7 @@ config SCSI_HISI_SAS
>> depends on ARM64 || COMPILE_TEST
>> select SCSI_SAS_LIBSAS
>> select BLK_DEV_INTEGRITY
>> + select RAS
>
>
> My impression is that we don't want this. Correction: shouldn't want this.
>
> Do you have the .config for the broken build? I couldn't recreate this by
> turning off CONFIG_RAS.
Uploaded to https://pastebin.com/A1rJYhDr
Maybe you were missing support for tracing in your configuration?
Arnd
Powered by blists - more mailing lists