From: Thomas Gleixner <tglx@linutronix•de>
To: Steven Rostedt <rostedt@goodmis•org>,
Linus Torvalds <torvalds@linux-foundation•org>
Cc: LKML <linux-kernel@vger•kernel.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>,
linux-sh@vger•kernel.org, linux-kernel@vger•kernel.org,
cgroups@vger•kernel.org, linux-block@vger•kernel.org,
linux-acpi@vger•kernel.org,
linux-atm-general@lists•sourceforge.net, netdev@vger•kernel.org,
drbd-dev@lists•linbit.com, linux-bluetooth@vger•kernel.org,
intel-gfx@lists•freedesktop.org, dri-devel@lists•freedesktop.org,
linux-input@vger•kernel.org, linux-leds@vger•kernel.org,
linux-media@vger•kernel.org, intel-wired-lan@lists•osuosl.org,
linux-usb@vger•kernel.org, linux-wireless@vger•kernel.org,
linux-scsi@vger•kernel.org, linux-staging@lists•linux.dev,
linux-ext4@vger•kernel.org, linux-nilfs@vger•kernel.org,
bridge@lists•linux-foundation.org,
netfilter-devel@vger•kernel.org, coreteam@netfilter•org,
lvs-devel@vger•kernel.org, linux-afs@lists•infradead.org,
linux-nfs@vger•kernel.org, tipc-discussion@lists•sourceforge.net,
alsa-devel@alsa-project•org
Subject: Re: [GIT PULL] treewide: timers: Use timer_shutdown*() before freeing timers
Date: Mon, 07 Nov 2022 11:47:04 +0100 [thread overview]
Message-ID: <87pmdzvy6v.ffs@tglx> (raw)
In-Reply-To: <20221106223256.4bbdb018@rorschach.local.home>
Linus,
On Sun, Nov 06 2022 at 22:32, Steven Rostedt wrote:
> As discussed here:
>
> https://lore.kernel.org/all/20221106212427.739928660@goodmis.org/
Please hold off. It's only nits, but tip has documented rules and random
pull requests are not making them go away.
Thanks,
tglx
prev parent reply other threads:[~2022-11-07 10:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 3:32 [GIT PULL] treewide: timers: Use timer_shutdown*() before freeing timers Steven Rostedt
2022-11-07 10:47 ` Thomas Gleixner [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=87pmdzvy6v.ffs@tglx \
--to=tglx@linutronix$(echo .)de \
--cc=Julia.Lawall@inria$(echo .)fr \
--cc=akpm@linux-foundation$(echo .)org \
--cc=alsa-devel@alsa-project$(echo .)org \
--cc=anna-maria@linutronix$(echo .)de \
--cc=bridge@lists$(echo .)linux-foundation.org \
--cc=cgroups@vger$(echo .)kernel.org \
--cc=coreteam@netfilter$(echo .)org \
--cc=drbd-dev@lists$(echo .)linbit.com \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=intel-wired-lan@lists$(echo .)osuosl.org \
--cc=linux-acpi@vger$(echo .)kernel.org \
--cc=linux-afs@lists$(echo .)infradead.org \
--cc=linux-atm-general@lists$(echo .)sourceforge.net \
--cc=linux-block@vger$(echo .)kernel.org \
--cc=linux-bluetooth@vger$(echo .)kernel.org \
--cc=linux-ext4@vger$(echo .)kernel.org \
--cc=linux-input@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-leds@vger$(echo .)kernel.org \
--cc=linux-media@vger$(echo .)kernel.org \
--cc=linux-nfs@vger$(echo .)kernel.org \
--cc=linux-nilfs@vger$(echo .)kernel.org \
--cc=linux-scsi@vger$(echo .)kernel.org \
--cc=linux-sh@vger$(echo .)kernel.org \
--cc=linux-staging@lists$(echo .)linux.dev \
--cc=linux-usb@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=linux@roeck-us$(echo .)net \
--cc=lvs-devel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=netfilter-devel@vger$(echo .)kernel.org \
--cc=rostedt@goodmis$(echo .)org \
--cc=sboyd@kernel$(echo .)org \
--cc=tipc-discussion@lists$(echo .)sourceforge.net \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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