From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tariq Toukan <tariqt@nvidia.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
linux-kernel@vger.kernel.org, Mark Bloch <mbloch@nvidia.com>,
Gal Pressman <gal@nvidia.com>, Aya Levin <ayal@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Simon Horman <horms@kernel.org>, Shay Drory <shayd@nvidia.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Parav Pandit <parav@nvidia.com>, Amir Tzin <amirtz@nvidia.com>
Subject: Re: [PATCH net] driver core: auxiliary bus: Fix sysfs creation on bind
Date: Thu, 23 Oct 2025 08:47:12 +0200 [thread overview]
Message-ID: <2025102355-abstract-subgroup-aa97@gregkh> (raw)
In-Reply-To: <1761200367-922346-1-git-send-email-tariqt@nvidia.com>
On Thu, Oct 23, 2025 at 09:19:27AM +0300, Tariq Toukan wrote:
> From: Amir Tzin <amirtz@nvidia.com>
>
> In case an auxiliary device with IRQs directory is unbinded, the
> directory is released, but auxdev->sysfs.irq_dir_exists remains true.
> This leads to a failure recreating the directory on bind [1].
>
> Using the attributes group visibility interface, expose the IRQs
> attributes group if"f the xarray storing IRQs entries is not empty. Now
> irq_dir_exists field is redundant and can be removed.
>
> [1]
> [] mlx5_core.sf mlx5_core.sf.2: mlx5_irq_affinity_request:167:(pid 1939):
> Failed to create sysfs entry for irq 56, ret = -2
> [] mlx5_core.sf mlx5_core.sf.2: mlx5_eq_table_create:1195:(pid 1939):
> Failed to create async EQs
> [] mlx5_core.sf mlx5_core.sf.2: mlx5_load:1362:(pid 1939):
> Failed to create EQs
>
> Fixes: a808878308a8 ("driver core: auxiliary bus: show auxiliary device IRQs")
> Signed-off-by: Amir Tzin <amirtz@nvidia.com>
> Reviewed-by: Mark Bloch <mbloch@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
> ---
> drivers/base/auxiliary.c | 13 +++-
> drivers/base/auxiliary_sysfs.c | 117 +++++++++++++++++++++++++--------
> include/linux/auxiliary_bus.h | 26 ++++++--
Why would auxbus patches go through the net tree?
confused,
greg k-h
next prev parent reply other threads:[~2025-10-23 6:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 6:19 [PATCH net] driver core: auxiliary bus: Fix sysfs creation on bind Tariq Toukan
2025-10-23 6:46 ` Greg Kroah-Hartman
2025-10-23 7:14 ` Tariq Toukan
2025-10-23 8:03 ` Greg Kroah-Hartman
2025-10-23 6:47 ` Greg Kroah-Hartman [this message]
2025-10-23 7:08 ` Tariq Toukan
2025-10-26 7:15 ` Leon Romanovsky
-- strict thread matches above, loose matches on Subject: below --
2025-03-17 10:32 Mark Bloch
2025-03-17 13:16 ` Greg Kroah-Hartman
2025-03-17 13:22 ` Mark Bloch
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=2025102355-abstract-subgroup-aa97@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=amirtz@nvidia.com \
--cc=ayal@nvidia.com \
--cc=dakr@kernel.org \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=parav@nvidia.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=rafael@kernel.org \
--cc=saeedm@nvidia.com \
--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 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.