From: Steven Rostedt <rostedt@goodmis.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-security-module@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] linux++: delete some forward declarations
Date: Thu, 13 Jun 2024 16:10:12 -0400 [thread overview]
Message-ID: <20240613161012.1dd2ff60@rorschach.local.home> (raw)
In-Reply-To: <20240613130420.a62ed8965a73b0f8d35890d4@linux-foundation.org>
On Thu, 13 Jun 2024 13:04:20 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Thu, 13 Jun 2024 15:34:02 -0400 Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > On Thu, 13 Jun 2024 22:22:18 +0300
> > Alexey Dobriyan <adobriyan@gmail.com> wrote:
> >
> > > g++ doesn't like forward enum declarations:
> > >
> > > error: use of enum ‘E’ without previous declaration
> > > 64 | enum E;
> >
> > But we don't care about g++. Do we?
>
> It appears that g++ is a useful enum declaration detector.
>
> I'm curious to know how even the above warning was generated. Does g++
> work at all on Linux?
>
> > I would make that a separate patch.
>
> What are you referring to here?
The enum change should be separate from the struct changes.
>
> > >
> > > Delete those which aren't used.
> > >
> > > Delete some unused/unnecessary forward struct declarations for a change.
> >
> > This is a clean up, but should have a better change log. Just something
> > simple like:
> >
> > Delete unnecessary forward struct declarations.
>
> Alexey specializes in cute changelogs.
eh
>
> I do have a concern about the patch: has it been tested with all
> possible Kconfigs? No. There may be some configs in which the forward
> declaration is required.
>
> And... I'm a bit surprised that forward declarations are allowed in C.
> A billion years ago I used a C compiler which would use 16 bits for
> an enum if the enumted values would fit in 16 bits. And it would use 32
> bits otherwise. So the enumerated values were *required* for the
> compiler to be able to figure out the sizeof. But it was a billion
> years ago.
Well, I only looked at the one change in ftrace.h which has a
"struct seq_file;" that is not used anywhere else in the file, so that
one definitely can go.
-- Steve
next prev parent reply other threads:[~2024-06-13 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 19:22 [PATCH] linux++: delete some forward declarations Alexey Dobriyan
2024-06-13 19:34 ` Steven Rostedt
2024-06-13 20:04 ` Andrew Morton
2024-06-13 20:10 ` Steven Rostedt [this message]
2024-06-13 21:21 ` Andrew Morton
2024-06-13 21:28 ` Steven Rostedt
2024-06-14 6:29 ` Alexey Dobriyan
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=20240613161012.1dd2ff60@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-trace-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 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).