Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Ryo Takakura <ryotkkr98@gmail.com>
To: bigeasy@linutronix.de, lgoncalv@redhat.com
Cc: bhelgaas@google.com, jonathan.derrick@linux.dev,
	kbusch@kernel.org, kw@linux.com, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, linux-rt-devel@lists.linux.dev,
	lpieralisi@kernel.org, manivannan.sadhasivam@linaro.org,
	nirmal.patel@linux.intel.com, robh@kernel.org,
	rostedt@goodmis.org
Subject: Re: [PATCH v3] PCI: vmd: Fix spinlock usage on config access for RT kernel
Date: Tue, 18 Feb 2025 23:07:45 +0900	[thread overview]
Message-ID: <20250218140745.16065-1-ryotkkr98@gmail.com> (raw)
In-Reply-To: <20250218080934.IRRZ6B6h@linutronix.de>

Hi Luis and Sebastian,

Thanks for checking in.

On Tue, 18 Feb 2025 09:09:34 +0100, Sebastian Andrzej Siewior wrote:
>On 2025-02-17 13:50:37 [-0300], Luis Claudio R. Goncalves wrote:
>> On Thu, Dec 19, 2024 at 10:45:49AM +0900, Ryo Takakura wrote:
>> > PCI config access is locked with pci_lock which is raw_spinlock.
>> > Convert cfg_lock to raw_spinlock so that the lock usage is consistent
>> > for RT kernel.
>> 
>> Any movement here?
>
>Reposted as https://lore.kernel.org/all/20250218080830.ufw3IgyX@linutronix.de

Thanks for the update!

Sincerely,
Ryo Takakura

      reply	other threads:[~2025-02-18 14:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19  1:45 [PATCH v3] PCI: vmd: Fix spinlock usage on config access for RT kernel Ryo Takakura
2025-02-17 16:50 ` Luis Claudio R. Goncalves
2025-02-18  8:09   ` Sebastian Andrzej Siewior
2025-02-18 14:07     ` Ryo Takakura [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=20250218140745.16065-1-ryotkkr98@gmail.com \
    --to=ryotkkr98@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=bigeasy@linutronix.de \
    --cc=jonathan.derrick@linux.dev \
    --cc=kbusch@kernel.org \
    --cc=kw@linux.com \
    --cc=lgoncalv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=nirmal.patel@linux.intel.com \
    --cc=robh@kernel.org \
    --cc=rostedt@goodmis.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