linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Rolf Eike Beer <eb@emlix.com>
Cc: Eric Biederman <ebiederm@xmission.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ELF uapi: add spaces before '{'
Date: Wed, 5 Oct 2022 20:33:08 -0700	[thread overview]
Message-ID: <202210052030.6B472DFCB5@keescook> (raw)
In-Reply-To: <11563980.Ss37MnutNL@mobilepool36.emlix.com>

On Tue, Oct 04, 2022 at 12:25:40PM +0200, Rolf Eike Beer wrote:
> When searching for a struct definition I often enough end up simply doing
> 
>   git grep 'struct foobar {'
> 
> Sadly some of the ELF structs did not follow the usual coding style so they
> were invisible.

Thanks! Yes, I do the same. :)

I'll get this into -next after the merge window closes.

-Kees

-- 
Kees Cook


  reply	other threads:[~2022-10-06  3:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 10:25 [PATCH] ELF uapi: add spaces before '{' Rolf Eike Beer
2022-10-06  3:33 ` Kees Cook [this message]
2022-10-18  7:22 ` Kees Cook

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=202210052030.6B472DFCB5@keescook \
    --to=keescook@chromium.org \
    --cc=eb@emlix.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).