From: Steven Rostedt <rostedt@goodmis.org>
To: Jakob Koschel <jakobkoschel@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, Mike Rapoport <rppt@kernel.org>,
Brian Johannesmeyer <bjohannesmeyer@gmail.com>,
Cristiano Giuffrida <c.giuffrida@vu.nl>,
"Bos, H.J." <h.j.bos@vu.nl>
Subject: Re: [PATCH] ftrace: remove check of list iterator against head past the loop body
Date: Thu, 31 Mar 2022 19:34:11 -0400 [thread overview]
Message-ID: <20220331193411.2fdbeb88@gandalf.local.home> (raw)
In-Reply-To: <212AE797-912E-47D1-9DC4-03B5351AFC57@gmail.com>
On Fri, 1 Apr 2022 01:22:58 +0200
Jakob Koschel <jakobkoschel@gmail.com> wrote:
> > Can you move this to the first declaration to keep the nice "upside-down
> > x-mas tree" look.
>
> Thanks, I'll fix that up. It seems like this is not applied on the entire kernel
> making treewide changes a bit more difficult. Is it documented somewhere, which
> parts of the kernel enforce this? Just looking two lines down from here it
> seems to be 'broken' already so just from looking at existing code it's often
> hard to judge.
It's one of those things that some maintainers prefer (I'm one of them ;-)
because it makes it easier to read IMHO.
But as you noticed, it's broken even in the same file. That's because I
don't strictly enforce it. If there's a lot of code that looks good to go
in, I don't ask to fix it. But as this was a small trivial patch, I figured
I'd mention it.
Thus, it's something that you do when asked, but don't worry about doing it
across the board, you are not going to upset anybody by forgetting to do it.
-- Steve
next prev parent reply other threads:[~2022-03-31 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 22:37 Jakob Koschel
2022-03-31 23:10 ` Steven Rostedt
2022-03-31 23:22 ` Jakob Koschel
2022-03-31 23:34 ` Steven Rostedt [this message]
2022-03-31 23:39 ` Jakob Koschel
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=20220331193411.2fdbeb88@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bjohannesmeyer@gmail.com \
--cc=c.giuffrida@vu.nl \
--cc=h.j.bos@vu.nl \
--cc=jakobkoschel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rppt@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
all inboxes | Powered by JetHome®