From: James Morris <jmorris@namei.org>
To: kernel test robot <lkp@intel.com>
Cc: Micah Morton <mortonm@chromium.org>,
linux-security-module@vger.kernel.org, llvm@lists.linux.dev,
kbuild-all@lists.01.org, keescook@chromium.org,
serge@hallyn.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] security: Add LSM hook to setgroups() syscall
Date: Wed, 15 Jun 2022 03:30:23 +1000 (AEST) [thread overview]
Message-ID: <ddcc855c-d8f-98ff-24c5-3abe24c1fe@namei.org> (raw)
In-Reply-To: <202206141619.gvenMkdS-lkp@intel.com>
On Tue, 14 Jun 2022, kernel test robot wrote:
> Hi Micah,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on linus/master]
> [also build test ERROR on jmorris-security/next-testing kees/for-next/pstore v5.19-rc2 next-20220614]
My next-testing is out of date, I'll push a newer version.
--
James Morris
<jmorris@namei.org>
WARNING: multiple messages have this Message-ID (diff)
From: James Morris <jmorris@namei.org>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 1/2] security: Add LSM hook to setgroups() syscall
Date: Wed, 15 Jun 2022 03:30:23 +1000 [thread overview]
Message-ID: <ddcc855c-d8f-98ff-24c5-3abe24c1fe@namei.org> (raw)
In-Reply-To: <202206141619.gvenMkdS-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 370 bytes --]
On Tue, 14 Jun 2022, kernel test robot wrote:
> Hi Micah,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on linus/master]
> [also build test ERROR on jmorris-security/next-testing kees/for-next/pstore v5.19-rc2 next-20220614]
My next-testing is out of date, I'll push a newer version.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2022-06-14 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 20:28 [PATCH 1/2] security: Add LSM hook to setgroups() syscall Micah Morton
2022-06-14 2:48 ` kernel test robot
2022-06-14 5:27 ` kernel test robot
2022-06-14 8:51 ` kernel test robot
2022-06-14 17:30 ` James Morris [this message]
2022-06-14 17:30 ` James Morris
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=ddcc855c-d8f-98ff-24c5-3abe24c1fe@namei.org \
--to=jmorris@namei.org \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mortonm@chromium.org \
--cc=serge@hallyn.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.