From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752216AbeDBOzu (ORCPT ); Mon, 2 Apr 2018 10:55:50 -0400 Received: from mga03.intel.com ([134.134.136.65]:13570 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751965AbeDBOzq (ORCPT ); Mon, 2 Apr 2018 10:55:46 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,395,1517904000"; d="scan'208";a="216842713" Message-ID: <1522680941.21176.180.camel@linux.intel.com> Subject: Re: [tip:x86/urgent] x86/io: Define readq()/writeq() to use 64-bit type From: Andy Shevchenko To: Ingo Molnar , Andy Shevchenko Cc: "H. Peter Anvin" , "Peter Zijlstra (Intel)" , Thomas Gleixner , Linus Torvalds , Linux Kernel Mailing List , kbuild test robot , sohil.mehta@intel.com, mitake@dcl.info.waseda.ac.jp, linux-tip-commits@vger.kernel.org Date: Mon, 02 Apr 2018 17:55:41 +0300 In-Reply-To: <20180331184528.dwpmpkpjj6ocwqhp@gmail.com> References: <20180119143322.16555-1-andriy.shevchenko@linux.intel.com> <1522163426.21176.24.camel@linux.intel.com> <20180331101914.ylrlgxhdohcosbnr@gmail.com> <20180331102220.kmtu62uktmfrfe4a@gmail.com> <20180331184528.dwpmpkpjj6ocwqhp@gmail.com> Organization: Intel Finland Oy Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.5-1+b1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 2018-03-31 at 20:45 +0200, Ingo Molnar wrote: > * Andy Shevchenko wrote: > > > On Sat, Mar 31, 2018 at 3:06 PM, Andy Shevchenko > > wrote: > > > On Sat, Mar 31, 2018 at 1:22 PM, Ingo Molnar > > > wrote: > > > > * Ingo Molnar wrote: > > > > [tip:x86/urgent 14/14] > > > > drivers/infiniband/hw/hns/hns_roce_hw_v1.c:1690:22: sparse: > > > > incorrect type in argument 1 (different base types) > > > > > > > > Since you were on Cc: of that report I assumed you'd take care > > > > of it. > > > > > > Ah, yes. This one I fixed. > > > > https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/commit > > /?h=for-next&id=71591d1280e5ef02c2af2ffb9801d0c842973be9 > > Yeah, so this fix in the RDMA tree needs to go upstream first, before > we can apply > the changes to the interface. Could you resend at around v4.17-rc1 or > so? Sure. Thanks! -- Andy Shevchenko Intel Finland Oy