From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Martin K. Petersen" Subject: Re: [PATCHv3 2/5] scsi: Export blacklist flags to sysfs Date: Tue, 15 Aug 2017 22:03:02 -0400 Message-ID: References: <1502461401-94630-1-git-send-email-hare@suse.de> <1502461401-94630-3-git-send-email-hare@suse.de> <1502807056.2900.1.camel@wdc.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from userp1040.oracle.com ([156.151.31.81]:20296 "EHLO userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753135AbdHPCDb (ORCPT ); Tue, 15 Aug 2017 22:03:31 -0400 In-Reply-To: (Hannes Reinecke's message of "Tue, 15 Aug 2017 16:40:11 +0200") Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Hannes Reinecke Cc: Bart Van Assche , "martin.petersen@oracle.com" , "hch@lst.de" , "james.bottomley@hansenpartnership.com" , "linux-scsi@vger.kernel.org" , "hare@suse.com" , "stern@rowland.harvard.edu" Hannes, >> Wouldn't debugfs be more appropriate for this attribute than sysfs? >> > I so don't mind. > I just need it somewhere in sysfs/debugfs so that I can validate the > selection logic. > > Same goes for hexvalue vs decoded output; I just need to attribute; > contents can be discussed. I don't have a problem having it in sysfs. We have several users that tweak the device blacklist in their boot scripts Given that we already have an interface for setting the flags, we might as well be able to print them. -- Martin K. Petersen Oracle Linux Engineering