Messages in this thread | | | From | Andy Shevchenko <> | Date | Sat, 31 Mar 2018 15:05:31 +0300 | Subject | Re: [tip:x86/urgent] x86/io: Define readq()/writeq() to use 64-bit type |
| |
On Sat, Mar 31, 2018 at 1:19 PM, Ingo Molnar <mingo@kernel.org> wrote: > > * Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote: > >> On Tue, 2018-02-13 at 08:58 -0800, tip-bot for Andy Shevchenko wrote: >> > Commit-ID: 0fc8483b698620ea3d8cc6635b54eccc613c23a3 >> > Gitweb: https://git.kernel.org/tip/0fc8483b698620ea3d8cc6635b54ecc >> > c613c23a3 >> > Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com> >> > AuthorDate: Fri, 19 Jan 2018 16:33:22 +0200 >> > Committer: Ingo Molnar <mingo@kernel.org> >> > CommitDate: Tue, 13 Feb 2018 17:14:41 +0100 >> >> 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?
Who knows? )
> Anyway, it's a good thing you kept out an eye for this: I re-applied the patch for > v4.17 and will let you know if there's any problem in testing.
Actually I got the same warning when tried to do some debug printings with readq() as a parameter. That's why I have noticed.
Thank you for re-applying!
-- With Best Regards, Andy Shevchenko
| |