From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Shravan Kumar Ramani <shravankr@nvidia.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Vadim Pasternak <vadimp@nvidia.com>,
David Thompson <davthompson@nvidia.com>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/4] platform/mellanox: mlxbf-pmc: Replace uintN_t with kernel-style types
Date: Fri, 9 Feb 2024 16:59:59 +0200 (EET) [thread overview]
Message-ID: <6905cf50-3314-2b3c-9bbf-eeb8000f0b54@linux.intel.com> (raw)
In-Reply-To: <73cd5e838695f8e20b022a523dcade108685350b.1707466888.git.shravankr@nvidia.com>
On Fri, 9 Feb 2024, Shravan Kumar Ramani wrote:
Hi,
You need to provice commit description here too. The shortlog on subject
line is not enough.
> Signed-off-by: Shravan Kumar Ramani <shravankr@nvidia.com>
> ---
> drivers/platform/mellanox/mlxbf-pmc.c | 121 +++++++++++++-------------
> 1 file changed, 59 insertions(+), 62 deletions(-)
>
> diff --git a/drivers/platform/mellanox/mlxbf-pmc.c b/drivers/platform/mellanox/mlxbf-pmc.c
> index b1995ac268d7..71d919832e2a 100644
> --- a/drivers/platform/mellanox/mlxbf-pmc.c
> +++ b/drivers/platform/mellanox/mlxbf-pmc.c
> @@ -149,17 +149,17 @@ struct mlxbf_pmc_block_info {
> */
> struct mlxbf_pmc_context {
> struct platform_device *pdev;
> - uint32_t total_blocks;
> - uint32_t tile_count;
> - uint8_t llt_enable;
> - uint8_t mss_enable;
> - uint32_t group_num;
> + u32 total_blocks;
> + u32 tile_count;
> + u8 llt_enable;
> + u8 mss_enable;
> + u32 group_num;
> struct device *hwmon_dev;
> const char *block_name[MLXBF_PMC_MAX_BLOCKS];
> struct mlxbf_pmc_block_info block[MLXBF_PMC_MAX_BLOCKS];
> const struct attribute_group *groups[MLXBF_PMC_MAX_BLOCKS];
> bool svc_sreg_support;
> - uint32_t sreg_tbl_perf;
> + u32 sreg_tbl_perf;
> unsigned int event_set;
> };
>
> @@ -865,8 +865,8 @@ static struct mlxbf_pmc_context *pmc;
> static const char *mlxbf_pmc_svc_uuid_str = "89c036b4-e7d7-11e6-8797-001aca00bfc4";
>
> /* Calls an SMC to access a performance register */
> -static int mlxbf_pmc_secure_read(void __iomem *addr, uint32_t command,
> - uint64_t *result)
> +static int mlxbf_pmc_secure_read(void __iomem *addr, u32 command,
> + u64 *result)
Please remove unnecessary newlines too such as this one from the function
arguments.
Other than those two things, this one looked fine. Thanks for doing this.
--
i.
next prev parent reply other threads:[~2024-02-09 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 8:39 [PATCH v2 0/4] Updates to mlxbf-pmc Shravan Kumar Ramani
2024-02-09 8:39 ` [PATCH v2 1/4] platform/mellanox: mlxbf-pmc: Replace uintN_t with kernel-style types Shravan Kumar Ramani
2024-02-09 14:59 ` Ilpo Järvinen [this message]
2024-02-09 8:39 ` [PATCH v2 2/4] platform/mellanox: mlxbf-pmc: Fix signed/unsigned mix-up Shravan Kumar Ramani
2024-02-09 15:08 ` Ilpo Järvinen
2024-02-09 8:39 ` [PATCH v2 3/4] platform/mellanox: mlxbf-pmc: Add support for 64-bit counters and cycle count Shravan Kumar Ramani
2024-02-09 8:39 ` [PATCH v2 4/4] platform/mellanox: mlxbf-pmc: Add support for clock_measure performance block Shravan Kumar Ramani
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=6905cf50-3314-2b3c-9bbf-eeb8000f0b54@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=davthompson@nvidia.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=shravankr@nvidia.com \
--cc=vadimp@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