All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: hpa@zytor.com, peterz@infradead.org, tglx@linutronix.de,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	lkp@intel.com, sohil.mehta@intel.com,
	mitake@dcl.info.waseda.ac.jp, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86/io: Define readq()/writeq() to use 64-bit type
Date: Sat, 31 Mar 2018 12:22:20 +0200	[thread overview]
Message-ID: <20180331102220.kmtu62uktmfrfe4a@gmail.com> (raw)
In-Reply-To: <20180331101914.ylrlgxhdohcosbnr@gmail.com>


* Ingo Molnar <mingo@kernel.org> 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.

Thanks,

	Ingo

  reply	other threads:[~2018-03-31 10:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19 14:33 [PATCH v1] x86/io: Define readq()/writeq() to use 64-bit type Andy Shevchenko
2018-01-23  0:32 ` Mehta, Sohil
2018-01-23  0:46   ` hpa
2018-01-23  8:32     ` Andy Shevchenko
2018-01-29 15:45       ` Andy Shevchenko
2018-02-13 16:58 ` [tip:x86/urgent] " tip-bot for Andy Shevchenko
2018-03-27 15:10   ` Andy Shevchenko
2018-03-31 10:19     ` Ingo Molnar
2018-03-31 10:22       ` Ingo Molnar [this message]
2018-03-31 12:06         ` Andy Shevchenko
2018-03-31 12:15           ` Andy Shevchenko
2018-03-31 18:45             ` Ingo Molnar
2018-04-02 14:55               ` Andy Shevchenko
2018-04-24 16:51               ` Andy Shevchenko
2018-03-31 12:05       ` Andy Shevchenko
2018-03-31 10:20 ` [tip:x86/platform] " tip-bot for Andy Shevchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180331102220.kmtu62uktmfrfe4a@gmail.com \
    --to=mingo@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mitake@dcl.info.waseda.ac.jp \
    --cc=peterz@infradead.org \
    --cc=sohil.mehta@intel.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.