From: Jason Gunthorpe <jgg@ziepe.ca>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Shay Drory <shayd@nvidia.com>,
netdev@vger.kernel.org, pabeni@redhat.com, davem@davemloft.net,
kuba@kernel.org, edumazet@google.com, david.m.ertman@intel.com,
rafael@kernel.org, ira.weiny@intel.com,
linux-rdma@vger.kernel.org, leon@kernel.org, tariqt@nvidia.com,
Parav Pandit <parav@nvidia.com>
Subject: Re: [PATCH net-next v4 1/2] driver core: auxiliary bus: show auxiliary device IRQs
Date: Mon, 13 May 2024 20:06:16 -0300 [thread overview]
Message-ID: <ZkKc6BFEQsmjTbvl@ziepe.ca> (raw)
In-Reply-To: <5a3520fa-590f-48be-8594-de44ae4eb750@intel.com>
On Mon, May 13, 2024 at 10:33:18AM +0200, Przemek Kitszel wrote:
> What if I want to store some struct, potentially with need of some init
> call (say, there will be a spinlock there)?
Yes, that specific pattern is definately a bit tricky, I have a
version in iommufd and I think at least someplace else... A helper of
some sort would be nice and could do a bit more work to be optimal.
Jason
next prev parent reply other threads:[~2024-05-13 23:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 9:14 [PATCH net-next v4 0/2] Introduce auxiliary bus IRQs sysfs Shay Drory
2024-05-09 9:14 ` [PATCH net-next v4 1/2] driver core: auxiliary bus: show auxiliary device IRQs Shay Drory
2024-05-10 8:15 ` Greg KH
2024-05-10 12:54 ` Przemek Kitszel
2024-05-10 13:07 ` Greg KH
2024-05-10 14:01 ` Przemek Kitszel
2024-05-11 7:44 ` Greg KH
2024-05-12 7:30 ` Shay Drori
2024-05-12 15:32 ` Jason Gunthorpe
2024-05-13 8:33 ` Przemek Kitszel
2024-05-13 23:06 ` Jason Gunthorpe [this message]
2024-05-12 7:27 ` Shay Drori
2024-05-09 9:14 ` [PATCH net-next v4 2/2] net/mlx5: Expose SFs IRQs Shay Drory
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=ZkKc6BFEQsmjTbvl@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=ira.weiny@intel.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=rafael@kernel.org \
--cc=shayd@nvidia.com \
--cc=tariqt@nvidia.com \
/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;
as well as URLs for NNTP newsgroup(s).