From: Will Deacon <will.deacon@arm.com>
To: Kees Cook <keescook@chromium.org>
Cc: "George G. Davis" <george_davis@mentor.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>, Jiri Kosina <trivial@kernel.org>,
Julien Grall <julien.grall@arm.com>,
Kristina Martsenko <kristina.martsenko@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
"moderated list:ARM64 PORT (AARCH64 ARCHITECTURE)"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] ARM64: trivial: s/TIF_SECOMP/TIF_SECCOMP/ comment typo fix
Date: Thu, 6 Jun 2019 10:39:46 +0100 [thread overview]
Message-ID: <20190606093946.GA6795@fuggles.cambridge.arm.com> (raw)
In-Reply-To: <201906051503.010FF2AF@keescook>
On Wed, Jun 05, 2019 at 03:04:06PM -0700, Kees Cook wrote:
> On Wed, Jun 05, 2019 at 04:30:09PM -0400, George G. Davis wrote:
> > Fix a s/TIF_SECOMP/TIF_SECCOMP/ comment typo
> >
> > Cc: Jiri Kosina <trivial@kernel.org>
> > Signed-off-by: George G. Davis <george_davis@mentor.com>
>
> Sneaky missing "C"! :)
>
> Reviewed-by: Kees Cook <keescook@chromium.org>
I've already got a few arm64 patches for -rc4, so I'll include this one
in my pull as it's harmless.
Cheers,
Will
prev parent reply other threads:[~2019-06-06 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 20:30 George G. Davis
2019-06-05 20:30 ` [PATCH 2/3] treewide: trivial: fix s/poped/popped/ typo George G. Davis
2019-06-06 6:47 ` Steven Rostedt
2019-06-07 14:22 ` Masami Hiramatsu
2019-06-07 17:50 ` Jonathan Corbet
2019-06-05 20:30 ` [PATCH 3/3] staging: most: trivial: fix a couple of typos George G. Davis
2019-06-05 22:04 ` [PATCH 1/3] ARM64: trivial: s/TIF_SECOMP/TIF_SECCOMP/ comment typo fix Kees Cook
2019-06-06 9:39 ` Will Deacon [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=20190606093946.GA6795@fuggles.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=george_davis@mentor.com \
--cc=julien.grall@arm.com \
--cc=keescook@chromium.org \
--cc=kristina.martsenko@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mark.rutland@arm.com \
--cc=trivial@kernel.org \
--cc=wad@chromium.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
Powered by JetHome