From: Mike Snitzer <snitzer@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>,
kbuild-all@01.org
Subject: Re: [dm:block-dm-4.21-inflight 4/9] include/linux/percpu-defs.h:219:52: error: invalid operands to binary + (have 'struct disk_stats' and 'int')
Date: Wed, 12 Dec 2018 19:47:50 -0500 [thread overview]
Message-ID: <20181213004750.GA3663@redhat.com> (raw)
In-Reply-To: <201812130808.IbSg5wxo%fengguang.wu@intel.com>
On Wed, Dec 12 2018 at 7:44pm -0500,
kbuild test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git block-dm-4.21-inflight
> head: 847fb34c0a7f7bbfca9d6053316aafb864a550b2
No idea why the kbuild test robot is just testing random branches but
this code was just a point in time for the percpu inflight counter
patchset. Since merged into linux-block with full support for
CONFIG_SMP not being set.
I'll delete this old block-dm-4.21-inflight branch now though...
prev parent reply other threads:[~2018-12-13 0:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 0:44 [dm:block-dm-4.21-inflight 4/9] include/linux/percpu-defs.h:219:52: error: invalid operands to binary + (have 'struct disk_stats' and 'int') kbuild test robot
2018-12-13 0:47 ` Mike Snitzer [this message]
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=20181213004750.GA3663@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=kbuild-all@01.org \
--cc=lkp@intel.com \
--cc=mpatocka@redhat.com \
/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.