From: Shuah Khan <skhan@linuxfoundation.org>
To: Sherry Yang <sherry.yang@oracle.com>
Cc: Kees Cook <keescook@chromium.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/seccomp: Fix seccomp failure by adding missing headers
Date: Thu, 10 Feb 2022 11:14:36 -0700 [thread overview]
Message-ID: <9fb71ee9-37c8-575c-0ca7-5a849403f7d9@linuxfoundation.org> (raw)
In-Reply-To: <6FCDF584-C765-4344-A851-E623B2FCB9A6@oracle.com>
On 2/10/22 11:08 AM, Sherry Yang wrote:
> Yeah, -I works, but just with some compiler warnings.
>
warnings aren't good. Kees, hope you are okay with this.
> If warnings are acceptable, do I need to send V2 patch with -I?
>
> Sherry
>
No top posting please. No need to fix it to -I - please send v2
I can't find your patch on lore - not sure why.
Please cc linux-kselftest and linux-kernel@vger.kernel.org
Also run scripts/get_maintainer.pl for a complete list of recipients
for this patch.
thanks,
-- Shuah
next parent reply other threads:[~2022-02-10 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220202201118.13933-1-sherry.yang@oracle.com>
[not found] ` <203db09a-b048-1c1b-6609-d91e51e3c2f7@linuxfoundation.org>
[not found] ` <A8A651FC-37A5-4716-888B-F141E7241003@oracle.com>
[not found] ` <202202031219.792E9AFF@keescook>
[not found] ` <C340461A-6FD2-440A-8EFC-D7E85BF48DB5@oracle.com>
[not found] ` <b908237b-63ad-ff10-8d89-540d2cab842e@linuxfoundation.org>
[not found] ` <6FCDF584-C765-4344-A851-E623B2FCB9A6@oracle.com>
2022-02-10 18:14 ` Shuah Khan [this message]
2022-02-10 20:38 ` Sherry Yang
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=9fb71ee9-37c8-575c-0ca7-5a849403f7d9@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sherry.yang@oracle.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
all inboxes | Powered by JetHome®