From: Simon Horman <horms@kernel.org>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
przemyslaw.kitszel@intel.com, dawid.osuchowski@linux.intel.com
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1 09/15] ice: drop driver specific structure from fwlog code
Date: Tue, 22 Jul 2025 15:54:28 +0100 [thread overview]
Message-ID: <20250722145428.GM2459@horms.kernel.org> (raw)
In-Reply-To: <20250722104600.10141-10-michal.swiatkowski@linux.intel.com>
On Tue, Jul 22, 2025 at 12:45:54PM +0200, Michal Swiatkowski wrote:
> In debugfs pass ice_fwlog structure instead of ice_pf.
>
> The debgufs dirs specific for fwlog can be stored in fwlog structure.
>
> Add debugfs entry point to fwlog api.
>
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
...
> diff --git a/drivers/net/ethernet/intel/ice/ice_debugfs.c b/drivers/net/ethernet/intel/ice/ice_debugfs.c
...
> @@ -580,9 +569,10 @@ static const struct file_operations ice_debugfs_data_fops = {
>
> /**
> * ice_debugfs_fwlog_init - setup the debugfs directory
> - * @pf: the ice that is starting up
> + * @fwlog: pointer to the fwlog structure
> + * @root: debugfs root entry on which fwlog director will be registered
> */
> -void ice_debugfs_fwlog_init(struct ice_pf *pf)
> +void ice_debugfs_fwlog_init(struct ice_fwlog *fwlog, struct dentry *root)
> {
> struct dentry *fw_modules_dir;
> struct dentry **fw_modules;
> @@ -598,41 +588,39 @@ void ice_debugfs_fwlog_init(struct ice_pf *pf)
>
> pf->ice_debugfs_pf_fwlog = debugfs_create_dir("fwlog",
> pf->ice_debugfs_pf);
pf no longer exists in this context.
> - if (IS_ERR(pf->ice_debugfs_pf_fwlog))
> + if (IS_ERR(fwlog->debugfs))
> goto err_create_module_files;
>
> - fw_modules_dir = debugfs_create_dir("modules",
> - pf->ice_debugfs_pf_fwlog);
> + fw_modules_dir = debugfs_create_dir("modules", fwlog->debugfs);
> if (IS_ERR(fw_modules_dir))
> goto err_create_module_files;
...
next prev parent reply other threads:[~2025-07-22 14:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 10:45 [Intel-wired-lan] [PATCH iwl-next v1 00/15] Fwlog support in ixgbe Michal Swiatkowski
2025-07-22 10:45 ` [Intel-wired-lan] [PATCH iwl-next v1 01/15] ice: make fwlog functions static Michal Swiatkowski
2025-07-22 11:58 ` Loktionov, Aleksandr
2025-07-22 10:45 ` [Intel-wired-lan] [PATCH iwl-next v1 02/15] ice: move get_fwlog_data() to fwlog file Michal Swiatkowski
2025-07-22 12:02 ` Loktionov, Aleksandr
2025-07-23 4:48 ` Michal Swiatkowski
2025-07-22 10:45 ` [Intel-wired-lan] [PATCH iwl-next v1 03/15] ice: drop ice_pf_fwlog_update_module() Michal Swiatkowski
2025-07-22 12:06 ` Loktionov, Aleksandr
2025-07-22 10:45 ` [Intel-wired-lan] [PATCH iwl-next v1 04/15] ice: introduce ice_fwlog structure Michal Swiatkowski
2025-07-22 12:17 ` Loktionov, Aleksandr
2025-07-22 10:45 ` [Intel-wired-lan] [PATCH iwl-next v1 05/15] ice: add pdev into fwlog structure and use it for logging Michal Swiatkowski
2025-07-23 10:36 ` Loktionov, Aleksandr
2025-07-22 10:45 ` [Intel-wired-lan] [PATCH iwl-next v1 06/15] ice: allow calling custom send function in fwlog Michal Swiatkowski
2025-07-22 10:45 ` [Intel-wired-lan] [PATCH iwl-next v1 07/15] ice: move out debugfs init from fwlog Michal Swiatkowski
2025-07-22 10:45 ` [Intel-wired-lan] [PATCH iwl-next v1 08/15] ice: check for PF number outside the fwlog code Michal Swiatkowski
2025-07-23 10:38 ` Loktionov, Aleksandr
2025-07-22 10:45 ` [Intel-wired-lan] [PATCH iwl-next v1 09/15] ice: drop driver specific structure from " Michal Swiatkowski
2025-07-22 14:54 ` Simon Horman [this message]
2025-07-23 4:47 ` Michal Swiatkowski
2025-07-23 10:42 ` Loktionov, Aleksandr
2025-07-22 10:45 ` [Intel-wired-lan] [PATCH iwl-next v1 10/15] libie, ice: move fwlog admin queue to libie Michal Swiatkowski
2025-07-22 10:45 ` [Intel-wired-lan] [PATCH iwl-next v1 11/15] ice: move debugfs code to fwlog Michal Swiatkowski
2025-07-22 10:45 ` [Intel-wired-lan] [PATCH iwl-next v1 12/15] ice: prepare for moving file to libie Michal Swiatkowski
2025-07-22 10:45 ` [Intel-wired-lan] [PATCH iwl-next v1 13/15] ice: reregister fwlog after driver reinit Michal Swiatkowski
2025-07-22 10:45 ` [Intel-wired-lan] [PATCH iwl-next v1 14/15] ice, libie: move fwlog code to libie Michal Swiatkowski
2025-07-22 10:46 ` [Intel-wired-lan] [PATCH iwl-next v1 15/15] ixgbe: fwlog support for e610 Michal Swiatkowski
2025-07-23 0:45 ` kernel test robot
2025-07-23 12:12 ` [Intel-wired-lan] [PATCH iwl-next v1 00/15] Fwlog support in ixgbe Jiri Pirko
2025-07-23 12:48 ` Michal Swiatkowski
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=20250722145428.GM2459@horms.kernel.org \
--to=horms@kernel.org \
--cc=dawid.osuchowski@linux.intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.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