linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org,
	Florian Fainelli <f.fainelli@gmail.com>,
	Tomohiro Kusumi <tkusumi@tuxera.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ian Kent <raven@themaw.net>, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] autofs: Revert wait_queue_t => wait_queue_entry_t rename
Date: Mon, 10 Jul 2017 16:52:22 +0800	[thread overview]
Message-ID: <201707101645.dOK79hDf%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170710044018.12474-1-f.fainelli@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1701 bytes --]

Hi Florian,

[auto build test ERROR on linus/master]
[cannot apply to v4.12]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Florian-Fainelli/autofs-Revert-wait_queue_t-wait_queue_entry_t-rename/20170710-140256
config: x86_64-rhel (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   fs/autofs4/waitq.c: In function 'autofs4_notify_daemon':
>> fs/autofs4/waitq.c:123:5: error: 'struct autofs_packet_missing' has no member named 'wait_queue_entry_token'; did you mean 'wait_queue_token'?
      mp->wait_queue_entry_token = wq->wait_queue_entry_token;
        ^~
>> fs/autofs4/waitq.c:136:5: error: 'struct autofs_packet_expire_multi' has no member named 'wait_queue_entry_token'; did you mean 'wait_queue_token'?
      ep->wait_queue_entry_token = wq->wait_queue_entry_token;
        ^~
>> fs/autofs4/waitq.c:156:9: error: 'struct autofs_v5_packet' has no member named 'wait_queue_entry_token'; did you mean 'wait_queue_token'?
      packet->wait_queue_entry_token = wq->wait_queue_entry_token;
            ^~

vim +123 fs/autofs4/waitq.c


:::::: The code at line 123 was first introduced by commit
:::::: ac6424b981bce1c4bc55675c6ce11bfe1bbfa64f sched/wait: Rename wait_queue_t => wait_queue_entry_t

:::::: TO: Ingo Molnar <mingo@kernel.org>
:::::: CC: Ingo Molnar <mingo@kernel.org>

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 39441 bytes --]

  parent reply	other threads:[~2017-07-10  8:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03  8:39 [GIT PULL] scheduler changes for v4.13 Ingo Molnar
2017-07-10  4:19 ` Florian Fainelli
2017-07-10  4:40   ` [PATCH] autofs: Revert wait_queue_t => wait_queue_entry_t rename Florian Fainelli
2017-07-10  8:45     ` Ingo Molnar
2017-07-10  8:52     ` kbuild test robot [this message]
2017-07-10  9:42     ` kbuild test robot
2017-07-10 14:01     ` Gabriel C
2017-07-10 15:52       ` Florian Fainelli
2017-07-10 18:47       ` Linus Torvalds
2017-07-10 23:00         ` Florian Fainelli
2017-07-10  8:45   ` [GIT PULL] scheduler changes for v4.13 Ingo Molnar

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=201707101645.dOK79hDf%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=f.fainelli@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=raven@themaw.net \
    --cc=tkusumi@tuxera.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).