From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753187AbeCaMGq (ORCPT ); Sat, 31 Mar 2018 08:06:46 -0400 Received: from mail-qt0-f195.google.com ([209.85.216.195]:45237 "EHLO mail-qt0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753118AbeCaMGn (ORCPT ); Sat, 31 Mar 2018 08:06:43 -0400 X-Google-Smtp-Source: AIpwx49j6AgZmpDepDNnyMbSTkjKex7zkilKN42CwkTWb7iu71PNJOzEE79vYu2i410YCcsfLum0XMdplpXr1FMa+BU= MIME-Version: 1.0 In-Reply-To: <20180331102220.kmtu62uktmfrfe4a@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> From: Andy Shevchenko Date: Sat, 31 Mar 2018 15:06:41 +0300 Message-ID: Subject: Re: [tip:x86/urgent] x86/io: Define readq()/writeq() to use 64-bit type To: Ingo Molnar Cc: Andy Shevchenko , "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 Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Mar 31, 2018 at 1:22 PM, Ingo Molnar wrote: > > * Ingo Molnar wrote: > >> > As of today I don't see this in linux-next >> > >> > % git tag --contains 0fc8483b69862 >> > next-20180214 >> > next-20180215 >> > next-20180216 >> > >> > What happened to this change? >> >> Hm, so it's a real mystery: I merged it, then removed it 1.5 days later without >> reporting anything. According to the Git log timestamp the removal happened late >> at night, so maybe it was a tired typo? > > So just a few seconds after sending this I remembered why I zapped it: it was a > Sparse failure reported by the kbuild-test robot. > > Here's the report: > > [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. -- With Best Regards, Andy Shevchenko