linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeffrin Thalakkottoor <jeffrin@rajagiritech.edu.in>
To: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: PROBLEM: error due to conflicting types during build of kselftests
Date: Fri, 20 Apr 2018 23:33:53 +0530	[thread overview]
Message-ID: <CAG=yYwnMXFxHxCnYNWCb-HhpAb21kc5_e_6q-N_DRGhMVurPMQ@mail.gmail.com> (raw)

hello,

the following is the error found...
-----------------------------------------------------------------------------------
protection_keys.c:421:5: error: conflicting types for ‘pkey_set’
 int pkey_set(int pkey, unsigned long rights, unsigned long flags)
     ^~~~~~~~
------------------------------------------------------------------------------------

to reproduce this error...
make -C tools/testing/selftests

Details about software:

Linux debian 4.17.0-rc1+ #1 SMP Thu Apr 19 18:59:45 IST 2018 x86_64 GNU/Linux

GNU Make             4.2.1
Binutils             2.30
Util-linux           2.31.1
Mount                2.31.1
Linux C Library      2.27
Dynamic linker (ldd) 2.27
readlink: missing operand
Try 'readlink --help' for more information.
Procps               3.3.14
Kbd                  2.0.4
Console-tools        2.0.4
Sh-utils             8.28
Udev                 238

-- 
software engineer
rajagiri school of engineering and technology

             reply	other threads:[~2018-04-20 18:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 18:03 Jeffrin Thalakkottoor [this message]
2018-04-27 23:38 ` PROBLEM: error due to conflicting types during build of kselftests Randy Dunlap
2018-04-28 21:42   ` Jeffrin Thalakkottoor
2018-04-28 21:54     ` Randy Dunlap
2018-05-08 15:46       ` Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2018-04-20 14:51 Jeffrin Thalakkottoor

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='CAG=yYwnMXFxHxCnYNWCb-HhpAb21kc5_e_6q-N_DRGhMVurPMQ@mail.gmail.com' \
    --to=jeffrin@rajagiritech.edu.in \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.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).