mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jakob Koschel <jakobkoschel@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
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: Fri, 1 Apr 2022 01:39:48 +0200	[thread overview]
Message-ID: <F0AC0EC6-35F9-4A2F-836F-513C03A622EC@gmail.com> (raw)
In-Reply-To: <20220331193411.2fdbeb88@gandalf.local.home>



> On 1. Apr 2022, at 01:34, Steven Rostedt <rostedt@goodmis.org> wrote:
> 
> 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.

I'm happy to fix it, I was just checking coding-style.rst and checkpatch.pl
and was hoping to find this documented somewhere.

> 
> 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.

I guess then I'll stick with the strategy to incorporate when it's obvious
or to my knowledge (net/*) and otherwise fix when pointed out :)

Thanks for the additional info.

> 
> -- Steve

	Jakob


      reply	other threads:[~2022-03-31 23:39 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
2022-03-31 23:39       ` Jakob Koschel [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=F0AC0EC6-35F9-4A2F-836F-513C03A622EC@gmail.com \
    --to=jakobkoschel@gmail.com \
    --cc=bjohannesmeyer@gmail.com \
    --cc=c.giuffrida@vu.nl \
    --cc=h.j.bos@vu.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --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®