From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754402AbdJPPg4 (ORCPT ); Mon, 16 Oct 2017 11:36:56 -0400 Received: from esa1.hgst.iphmx.com ([68.232.141.245]:17073 "EHLO esa1.hgst.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754118AbdJPPgw (ORCPT ); Mon, 16 Oct 2017 11:36:52 -0400 X-IronPort-AV: E=Sophos;i="5.43,387,1503331200"; d="scan'208";a="160720264" From: Bart Van Assche To: "mst@redhat.com" CC: "hch@lst.de" , "linux-kernel@vger.kernel.org" , "linux-scsi@vger.kernel.org" , "torvalds@linux-foundation.org" , "qla2xxx-upstream@qlogic.com" , "martin.petersen@oracle.com" , "jejb@linux.vnet.ibm.com" Subject: Re: [PATCH] linux/types.h: Restore the ability to disable sparse endianness checks Thread-Topic: [PATCH] linux/types.h: Restore the ability to disable sparse endianness checks Thread-Index: AQHTPsfpNidr/j8ehUyvQHGzmN9zsKLbhcaAgAAdXoCAACtPAIABgFIAgAk6vQCAAAZbgIAAGTwAgAACgIA= Date: Mon, 16 Oct 2017 15:36:50 +0000 Message-ID: <1508168209.2493.13.camel@wdc.com> References: <20171006172353.16758-1-bart.vanassche@wdc.com> <20171009162008-mutt-send-email-mst@kernel.org> <1507561661.2674.3.camel@wdc.com> <20171009204139-mutt-send-email-mst@kernel.org> <1507653494.2815.27.camel@wdc.com> <20171016160316-mutt-send-email-mst@kernel.org> <1508162253.2728.1.camel@wdc.com> <20171016181159-mutt-send-email-mst@kernel.org> In-Reply-To: <20171016181159-mutt-send-email-mst@kernel.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=Bart.VanAssche@wdc.com; x-originating-ip: [63.163.107.201] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1;CY1PR0401MB1533;20:8U+eLIIwPWqejQ+F7tPWY84gNwSVovgFjOFPDnuYuO2OHap5aFn2l2KCbx5jwpkJqxkbavCmm5UXnNhMS4WuphSDuDiC0d0HdcZuZQPvNOe33AiWlKJ/MzDfX0XdZv4nhlD2BZgCm0rzismzkRxjCyGr8giE4titHmvaOUXMU74= x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: f3017d11-a6b6-43a0-37c7-08d514abb858 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001)(2017030254152)(48565401081)(2017052603199)(201703131423075)(201703031133081)(201702281549075);SRVR:CY1PR0401MB1533; x-ms-traffictypediagnostic: CY1PR0401MB1533: wdcipoutbound: EOP-TRUE x-exchange-antispam-report-test: UriScan:(84791874153150); x-microsoft-antispam-prvs: x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(3002001)(100000703101)(100105400095)(93006095)(93001095)(10201501046)(6055026)(6041248)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123560025)(20161123558100)(20161123555025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095);SRVR:CY1PR0401MB1533;BCL:0;PCL:0;RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095);SRVR:CY1PR0401MB1533; x-forefront-prvs: 0462918D61 x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(6009001)(39860400002)(346002)(376002)(51444003)(199003)(377424004)(24454002)(189002)(66066001)(5660300001)(105586002)(99286003)(81166006)(14454004)(2906002)(8676002)(7736002)(2351001)(93886005)(966005)(53936002)(102836003)(3846002)(305945005)(25786009)(97736004)(5640700003)(2501003)(33646002)(6246003)(8936002)(6512007)(4001150100001)(6116002)(316002)(36756003)(101416001)(2900100001)(103116003)(50986999)(189998001)(4326008)(478600001)(3660700001)(72206003)(1730700003)(6486002)(6506006)(106356001)(6436002)(77096006)(68736007)(3280700002)(54906003)(6306002)(81156014)(86362001)(76176999)(54356999)(6916009)(229853002)(2950100002);DIR:OUT;SFP:1102;SCL:1;SRVR:CY1PR0401MB1533;H:CY1PR0401MB1536.namprd04.prod.outlook.com;FPR:;SPF:None;PTR:InfoNoRecords;A:1;MX:1;LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" Content-ID: <9B5D22806935564BBE934C6C3803C1D6@namprd04.prod.outlook.com> MIME-Version: 1.0 X-OriginatorOrg: wdc.com X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Oct 2017 15:36:50.5826 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: b61c8803-16f3-4c35-9b17-6f65f441df86 X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0401MB1533 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id v9GFb2s0025329 On Mon, 2017-10-16 at 18:27 +0300, Michael S. Tsirkin wrote: > On Mon, Oct 16, 2017 at 01:57:35PM +0000, Bart Van Assche wrote: > > On Mon, 2017-10-16 at 16:34 +0300, Michael S. Tsirkin wrote: > > > I don't see how it'll help make things better. OTOH if the specific > > > drivers are tagged in the makefile, they can be gradually moved out to > > > staging or something to help trigger action. > > > > Do you really want to move drivers like qla2xxx to staging? That driver is > > important to multiple enterprise distro's. > > Frankly I'm surprised this one has sparse issues. > Really e.g. drivers/scsi/qla2xxx/qla_nvme.h is new from June 2017. > > It's not some ancient piece of code that no one understands so > we are afraid to touch it. Sorry if I wasn't clear enough but I wasn't referring to the qla2xxx NVMe code. I was referring to the qla2xxx FC initiator code. I think that code went upstream in January 2004. See also https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git/log/drivers/scsi/qla2xxx?ofs=100 Bart.