public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	x86@kernel.org, maz@kernel.org
Subject: Re: [tip: irq/core] genirq: Warn about using IRQF_ONESHOT without a threaded handler
Date: Tue, 13 Jan 2026 16:26:33 +0100	[thread overview]
Message-ID: <87ecntjzyu.ffs@tglx> (raw)
In-Reply-To: <20260113120541.YVf2vRA3@linutronix.de>

On Tue, Jan 13 2026 at 13:05, Sebastian Andrzej Siewior wrote:
> On 2026-01-13 08:58:56 [-0000], tip-bot2 for Sebastian Andrzej Siewior wrote:
>> The following commit has been merged into the irq/core branch of tip:
>> 
>> Commit-ID:     aef30c8d569c0f31715447525640044c74feb26f
>> Gitweb:        https://git.kernel.org/tip/aef30c8d569c0f31715447525640044c74feb26f
>> Author:        Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>> AuthorDate:    Mon, 12 Jan 2026 14:40:13 +01:00
>> Committer:     Thomas Gleixner <tglx@kernel.org>
>> CommitterDate: Tue, 13 Jan 2026 09:56:25 +01:00
>> 
>> genirq: Warn about using IRQF_ONESHOT without a threaded handler
>
> Should I pro-active send some patches to those users which I know do it
> wrong? Or do we simply wait?

Just send fixes for them ...

  reply	other threads:[~2026-01-13 15:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12 13:40 [PATCH] genirq: Warn about using IRQF_ONESHOT without a threaded handler Sebastian Andrzej Siewior
2026-01-12 17:46 ` Laurent Pinchart
2026-01-14 10:29   ` Stefan Klug
2026-01-13  8:58 ` [tip: irq/core] " tip-bot2 for Sebastian Andrzej Siewior
2026-01-13 12:05   ` Sebastian Andrzej Siewior
2026-01-13 15:26     ` Thomas Gleixner [this message]
2026-02-02 23:27     ` Bert Karwatzki
2026-02-03  8:38       ` Sebastian Andrzej Siewior
2026-02-03 10:43         ` Bert Karwatzki
2026-02-03 14:58           ` Sebastian Andrzej Siewior
2026-02-07 15:46             ` Jonathan Cameron
2026-02-09  2:00               ` srinivas pandruvada
2026-02-14 15:00                 ` Jonathan Cameron
2026-02-14 15:08                   ` Jonathan Cameron
2026-02-03 17:29         ` srinivas pandruvada
2026-02-07 15:42           ` Jonathan Cameron
2026-03-01 23:17             ` David Lechner
2026-03-01 23:57               ` David Lechner
2026-03-01 22:45         ` David Lechner

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=87ecntjzyu.ffs@tglx \
    --to=tglx@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=x86@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