All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
	stable-commits@vger.kernel.org, Thomas Gleixner <tglx@kernel.org>,
	Radu Rendec <radu@rendec.net>, Paul Walmsley <pjw@kernel.org>,
	Samuel Holland <samuel.holland@sifive.com>,
	Charles Mirabile <cmirabil@redhat.com>
Subject: Re: Patch "irqchip/sifive-plic: Cache the interrupt enable state" has been added to the 6.18-stable tree
Date: Tue, 17 Nov 2026 19:19:58 -0500	[thread overview]
Message-ID: <2026-11-17-1-daily-reply-0007@kernel.org> (raw)
In-Reply-To: <CABe3_aGGSWW2LrPHNtAU8Lc2NqgeOQJrZNma2WzQ-JH+vFyWJg@mail.gmail.com>

> This patch makes substantial changes to the driver and how it
> processes interrupts. I am not sure it is a great candidate for
> stable.

Agreed. I dropped it, and the BIT() fix that needed it, from the 6.18, 6.12,
6.6 and 6.1 queues. The same applies to your notices for the other three trees.

Could you send git-am-able BIT()-only backports of 0f214e5bbee5
("irqchip/sifive-plic: Avoid signed shift in interrupt enable mask"), one per
tree ([PATCH 6.18.y] through [PATCH 6.1.y])? I'll queue them. 7.3 already has
the cache patch in its base release, so it keeps the original fix.

-- 
Thanks,
Sasha

WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: stable-commits@vger.kernel.org, Thomas Gleixner <tglx@kernel.org>,
	Radu Rendec <radu@rendec.net>, Paul Walmsley <pjw@kernel.org>,
	Samuel Holland <samuel.holland@sifive.com>,
	Charles Mirabile <cmirabil@redhat.com>
Subject: Re: Patch "irqchip/sifive-plic: Cache the interrupt enable state" has been added to the 6.18-stable tree
Date: Tue, 17 Nov 2026 19:23:02 -0500	[thread overview]
Message-ID: <2026-11-17-1-daily-reply-0007@kernel.org> (raw)
Message-ID: <20261118002302.sb-OlvFHxkJpwI2OQl4hmui5lPJPyvzStBng3doKIOc@z> (raw)
In-Reply-To: <CABe3_aGGSWW2LrPHNtAU8Lc2NqgeOQJrZNma2WzQ-JH+vFyWJg@mail.gmail.com>

> This patch makes substantial changes to the driver and how it
> processes interrupts. I am not sure it is a great candidate for
> stable.

Agreed. I dropped it, and the BIT() fix that needed it, from the 6.18, 6.12,
6.6 and 6.1 queues. The same applies to your notices for the other three trees.

Could you send git-am-able BIT()-only backports of 0f214e5bbee5
("irqchip/sifive-plic: Avoid signed shift in interrupt enable mask"), one per
tree ([PATCH 6.18.y] through [PATCH 6.1.y])? I'll queue them. 7.3 already has
the cache patch in its base release, so it keeps the original fix.

-- 
Thanks,
Sasha

  reply	other threads:[~2026-11-18  0:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20261117161945.1965350-1-sashal@kernel.org>
2026-11-17 17:01 ` Patch "irqchip/sifive-plic: Cache the interrupt enable state" has been added to the 6.18-stable tree Charles Mirabile
2026-11-18  0:19   ` Sasha Levin [this message]
2026-11-18  0:23     ` Sasha Levin
2026-11-18  2:04     ` [PATCH] irqchip/sifive-plic: Avoid signed shift in interrupt enable mask Charles Mirabile

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=2026-11-17-1-daily-reply-0007@kernel.org \
    --to=sashal@kernel.org \
    --cc=cmirabil@redhat.com \
    --cc=pjw@kernel.org \
    --cc=radu@rendec.net \
    --cc=samuel.holland@sifive.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.