All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] linux/coff.h: add include guard
Date: Wed, 31 Jul 2019 18:23:01 +0900	[thread overview]
Message-ID: <CAK7LNATSaZVdFm4=mODoAUnjwf3QKS5Fx5drkZ-yGDHTabfPsQ@mail.gmail.com> (raw)
In-Reply-To: <20190730125249.b899526e44608371fb11e03c@linux-foundation.org>

Hi Andrew,

On Wed, Jul 31, 2019 at 4:52 AM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Mon, 29 Jul 2019 00:47:28 +0900 Masahiro Yamada <yamada.masahiro@socionext.com> wrote:
>
> > Add a header include guard just in case.
> >
> > Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> > ---
> >
> > Looks like this file is unused at least in the kernel tree,
> > but I am not it is OK to delete it.
>
> arch/alpha/boot/tools/objstrip.c includes it but I don't think it's
> actually needed.  Yes, it would be nice to kill coff.h.

After some consideration, I think it is better to keep it
until we dump the alpha support entirely.

The following line in arch/alpha/boot/tools/objstrip.c
references a macro in <linux/coff.h>:

        if (!(aout->fh.f_flags & COFF_F_EXEC)) {


I was not able to build objstrip.c anyway,
but I think it is better to keep the can of worms closed for now.


Could you apply this as-is please?


My motivation is to allow Kbuild to detect missing include guard:

https://patchwork.kernel.org/patch/11063011/


Before I enable this checker,
I want to fix as many headers as possible.



-- 
Best Regards
Masahiro Yamada

      reply	other threads:[~2019-07-31  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-28 15:47 [PATCH] linux/coff.h: add include guard Masahiro Yamada
2019-07-30 19:52 ` Andrew Morton
2019-07-31  9:23   ` Masahiro Yamada [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='CAK7LNATSaZVdFm4=mODoAUnjwf3QKS5Fx5drkZ-yGDHTabfPsQ@mail.gmail.com' \
    --to=yamada.masahiro@socionext.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.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 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.