From: Ingo Molnar <mingo@kernel.org>
To: Shuah Khan <shuah@kernel.org>
Cc: Dave Hansen <dave.hansen@intel.com>,
Li Zhijian <lizhijian@cn.fujitsu.com>,
linux-kselftest@vger.kernel.org, tglx@linutronix.de,
gregkh@linuxfoundation.org, pombredanne@nexb.com,
ebiederm@xmission.com, luto@kernel.org,
linux-kernel@vger.kernel.org, philip.li@intel.com,
leist.fnst@cn.fujitsu.com, zhijianx.li@intel.com
Subject: Re: [PATCH 1/2] tools/testing/selftests/x86: fix warning: "SEGV_PKUERR|SEGV_BNDERR" redefined
Date: Fri, 18 May 2018 12:10:10 +0200 [thread overview]
Message-ID: <20180518101010.GA924@gmail.com> (raw)
In-Reply-To: <68755e04-3954-e193-8ba3-e96930075622@kernel.org>
* Shuah Khan <shuah@kernel.org> wrote:
> On 05/14/2018 03:31 AM, Ingo Molnar wrote:
> >
> > * Shuah Khan <shuah@kernel.org> wrote:
> >
> >> On 05/08/2018 10:25 AM, Dave Hansen wrote:
> >>> On 05/08/2018 02:14 AM, Li Zhijian wrote:
> >>>> SEGV_PKUERR and SEGV_BNDERR are defined since glibc-2.27
> >>>
> >>>
> >>> Acked-by: Dave Hansen <dave.hansen@intel.com>
> >>>
> >>
> >> Thanks. Queuing this up for 4.17-rc5
> >
> > Please drop these patches, I have fixed them slightly differently and there are
> > dependencies with followup patches.
> >
> > Tanks,
> >
> > Ingo
> >
>
> Dropped now.
Thanks!
Ingo
prev parent reply other threads:[~2018-05-18 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 9:14 [PATCH 1/2] tools/testing/selftests/x86: fix warning: "SEGV_PKUERR|SEGV_BNDERR" redefined Li Zhijian
2018-05-08 9:14 ` [PATCH 2/2] tools/testing/selftests/x86: fix error: conflicting types for 'pkey_get|pkey_set' Li Zhijian
2018-05-08 16:30 ` Dave Hansen
2018-05-08 17:36 ` Shuah Khan
2018-05-14 9:30 ` Ingo Molnar
2018-05-08 16:25 ` [PATCH 1/2] tools/testing/selftests/x86: fix warning: "SEGV_PKUERR|SEGV_BNDERR" redefined Dave Hansen
2018-05-08 17:35 ` Shuah Khan
2018-05-14 9:31 ` Ingo Molnar
2018-05-15 20:08 ` Shuah Khan
2018-05-18 10:10 ` Ingo Molnar [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=20180518101010.GA924@gmail.com \
--to=mingo@kernel.org \
--cc=dave.hansen@intel.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=leist.fnst@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lizhijian@cn.fujitsu.com \
--cc=luto@kernel.org \
--cc=philip.li@intel.com \
--cc=pombredanne@nexb.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=zhijianx.li@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox