public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Stephen Boyd <sboyd@kernel.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Anna-Maria Gleixner <anna-maria@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Julia Lawall <Julia.Lawall@inria.fr>
Subject: Re: [for-linus][PATCH 4/5] timers: Add timer_shutdown_sync() and timer_shutdown() to be called before freeing timers
Date: Mon, 7 Nov 2022 23:15:32 -0500	[thread overview]
Message-ID: <20221107231532.4bbfce5c@rorschach.local.home> (raw)
In-Reply-To: <87y1sm8h1o.ffs@tglx>

On Tue, 08 Nov 2022 00:45:55 +0100
Thomas Gleixner <tglx@linutronix.de> wrote:

> > Sure, but I'm traveling this week and may not get to it until Friday.  
> 
> That's fine as I think this whole approach is wrong to begin with.
> 
> We are not doing a tree wide change at rc4 just to scratch an itch which
> is there for ages and has been debated for months.
> 
> Q: Did you try a merge of the result against -next?
> A: Definitely not.

OK, Yep, I was only working with Linus's tree, not next, something I
overlooked.

> 
> The proper approach is to provide all the infrastructure, i.e. the new
> interfaces and merge them during the next merge window. Right before rc1
> provide a script or a script converted tree to Linus which switches the
> tree over to the new world order.

Well, actually this was my original plan, but Linus asked for the
treewide script to be done in this -rc release, and that part was only
done on his request.

  https://lore.kernel.org/all/CAHk-=whKE5UL+AuCC2wK8oq8D_ueSO_T7-9Acx4POouqVi8ZHg@mail.gmail.com/


> 
> How long have you been around doing kernel development and how much fuzz
> do you make about even trivial changes to ftrace?

This is my first "treewide" change I'm doing, so I'm going to make
mistakes. Hence why I started this all off with RFC.

I'll rebase this on next and break this patch up into more comprehensible bits.

-- Steve

  reply	other threads:[~2022-11-08  4:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06 23:30 [for-linus][PATCH 0/5] timers: Use timer_shutdown*() before freeing timers Steven Rostedt
2022-11-06 23:30 ` [for-linus][PATCH 2/5] clocksource/drivers/arm_arch_timer: Do not use timer namespace for timer_shutdown() function Steven Rostedt
2022-11-06 23:30 ` [for-linus][PATCH 3/5] clocksource/drivers/sp804: " Steven Rostedt
2022-11-06 23:30 ` [for-linus][PATCH 4/5] timers: Add timer_shutdown_sync() and timer_shutdown() to be called before freeing timers Steven Rostedt
2022-11-07 10:27   ` Thomas Gleixner
2022-11-07 10:45   ` Thomas Gleixner
2022-11-07 11:15     ` Thomas Gleixner
2022-11-07 13:43       ` Steven Rostedt
2022-11-07 23:45         ` Thomas Gleixner
2022-11-08  4:15           ` Steven Rostedt [this message]
2022-11-06 23:30 ` [for-linus][PATCH 5/5] treewide: Convert del_timer*() to timer_shutdown*() Steven Rostedt

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=20221107231532.4bbfce5c@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=Julia.Lawall@inria.fr \
    --cc=akpm@linux-foundation.org \
    --cc=anna-maria@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=sboyd@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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