All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: Anup Patel <anup@brainfault.org>, Xu Lu <luxu.kernel@bytedance.com>
Cc: atish.patra@linux.dev, pjw@kernel.org, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, alex@ghiti.fr, kvm@vger.kernel.org,
	kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] irqchip/riscv-imsic: Adjust the number of available guest irq files
Date: Fri, 09 Jan 2026 13:32:05 +0100	[thread overview]
Message-ID: <874iovrmpm.ffs@tglx> (raw)
In-Reply-To: <CAAhSdy0dcMhmENZ9cMkE7Rh8u93sRiYozxEWgJ0tvHVUiRdykw@mail.gmail.com>

On Sun, Jan 04 2026 at 18:46, Anup Patel wrote:
> On Mon, Dec 22, 2025 at 3:07 PM Xu Lu <luxu.kernel@bytedance.com> wrote:
>
> Reviewed-by: Anup Patel <anup@brainfault.org>
>
> @tglx, Is it okay to take this through the KVM RISC-V tree
> since this change focuses on guest files used by KVM ?

Sure, if there are no conflicts against tip irq/drivers.

Acked-by: Thomas Gleixner <tglx@kernel.org>

-- 
kvm-riscv mailing list
kvm-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kvm-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@kernel.org>
To: Anup Patel <anup@brainfault.org>, Xu Lu <luxu.kernel@bytedance.com>
Cc: atish.patra@linux.dev, pjw@kernel.org, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, alex@ghiti.fr, kvm@vger.kernel.org,
	kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] irqchip/riscv-imsic: Adjust the number of available guest irq files
Date: Fri, 09 Jan 2026 13:32:05 +0100	[thread overview]
Message-ID: <874iovrmpm.ffs@tglx> (raw)
In-Reply-To: <CAAhSdy0dcMhmENZ9cMkE7Rh8u93sRiYozxEWgJ0tvHVUiRdykw@mail.gmail.com>

On Sun, Jan 04 2026 at 18:46, Anup Patel wrote:
> On Mon, Dec 22, 2025 at 3:07 PM Xu Lu <luxu.kernel@bytedance.com> wrote:
>
> Reviewed-by: Anup Patel <anup@brainfault.org>
>
> @tglx, Is it okay to take this through the KVM RISC-V tree
> since this change focuses on guest files used by KVM ?

Sure, if there are no conflicts against tip irq/drivers.

Acked-by: Thomas Gleixner <tglx@kernel.org>

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@kernel.org>
To: Anup Patel <anup@brainfault.org>, Xu Lu <luxu.kernel@bytedance.com>
Cc: atish.patra@linux.dev, pjw@kernel.org, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, alex@ghiti.fr, kvm@vger.kernel.org,
	kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] irqchip/riscv-imsic: Adjust the number of available guest irq files
Date: Fri, 09 Jan 2026 13:32:05 +0100	[thread overview]
Message-ID: <874iovrmpm.ffs@tglx> (raw)
In-Reply-To: <CAAhSdy0dcMhmENZ9cMkE7Rh8u93sRiYozxEWgJ0tvHVUiRdykw@mail.gmail.com>

On Sun, Jan 04 2026 at 18:46, Anup Patel wrote:
> On Mon, Dec 22, 2025 at 3:07 PM Xu Lu <luxu.kernel@bytedance.com> wrote:
>
> Reviewed-by: Anup Patel <anup@brainfault.org>
>
> @tglx, Is it okay to take this through the KVM RISC-V tree
> since this change focuses on guest files used by KVM ?

Sure, if there are no conflicts against tip irq/drivers.

Acked-by: Thomas Gleixner <tglx@kernel.org>

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-01-09 12:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-22  9:37 [PATCH v4] irqchip/riscv-imsic: Adjust the number of available guest irq files Xu Lu
2025-12-22  9:37 ` Xu Lu
2025-12-22  9:37 ` Xu Lu
2025-12-23  6:15 ` Nutty.Liu
2025-12-23  6:15   ` Nutty.Liu
2025-12-23  6:15   ` Nutty.Liu
2026-01-04 13:16 ` Anup Patel
2026-01-04 13:16   ` Anup Patel
2026-01-04 13:16   ` Anup Patel
2026-01-09 12:32   ` Thomas Gleixner [this message]
2026-01-09 12:32     ` Thomas Gleixner
2026-01-09 12:32     ` Thomas Gleixner

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=874iovrmpm.ffs@tglx \
    --to=tglx@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=atish.patra@linux.dev \
    --cc=kvm-riscv@lists.infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=luxu.kernel@bytedance.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@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.