public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Shuah Khan <skhan@linuxfoundation•org>
To: Kees Cook <keescook@chromium•org>,
	Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Shuah Khan <shuah@kernel•org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Christian Brauner <christian.brauner@ubuntu•com>,
	Shuah Khan <skhan@linuxfoundation•org>
Subject: Re: linux-next: manual merge of the seccomp tree with the kselftest tree
Date: Tue, 7 Jul 2020 13:27:59 -0600	[thread overview]
Message-ID: <18b266d0-a116-7201-6cd8-6e11f809e753@linuxfoundation.org> (raw)
In-Reply-To: <202007070125.ECBAB9E7C3@keescook>

On 7/7/20 2:26 AM, Kees Cook wrote:
> On Tue, Jul 07, 2020 at 02:57:20PM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> Today's linux-next merge of the seccomp tree got a conflict in:
>>
>>    tools/testing/selftests/seccomp/seccomp_bpf.c
>>
>> between commit:
>>
>>    9847d24af95c ("selftests/harness: Refactor XFAIL into SKIP")
>>
>> from the kselftest tree and commits:
>>
>>    aae7d264d68b ("selftests/seccomp: Check for EPOLLHUP for user_notif")
>>    11b4beaa0d31 ("selftests/seccomp: Make kcmp() less required")
>>    ef332c970dfa ("selftests/seccomp: Rename user_trap_syscall() to user_notif_syscall()")
>>
>> from the seccomp tree.
> 
> Har har -- a collision of my own creation. Yay lots of trees. ;) I'll
> make this go away; the cause is a harmless cleanup.
> 

Thanks Kees. Let me know if I have to do anything.

thanks,
-- Shuah

next prev parent reply	other threads:[~2020-07-07 19:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07  4:57 linux-next: manual merge of the seccomp tree with the kselftest tree Stephen Rothwell
2020-07-07  8:26 ` Kees Cook
2020-07-07 19:27   ` Shuah Khan [this message]
2020-07-08  2:00     ` Kees Cook
  -- strict thread matches above, loose matches on Subject: below --
2020-07-20  5:59 Stephen Rothwell
2020-08-05  5:45 ` Stephen Rothwell
2020-08-05 22:24   ` Shuah Khan
2020-08-05 22:27     ` Stephen Rothwell

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=18b266d0-a116-7201-6cd8-6e11f809e753@linuxfoundation.org \
    --to=skhan@linuxfoundation$(echo .)org \
    --cc=christian.brauner@ubuntu$(echo .)com \
    --cc=keescook@chromium$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=shuah@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox