All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shravan Kumar Ramani <shravankr@nvidia.com>
To: Hans de Goede <hdegoede@redhat.com>,
	Mark Gross <markgross@kernel.org>,
	Vadim Pasternak <vadimp@nvidia.com>,
	David Thompson <davthompson@nvidia.com>
Cc: Shravan Kumar Ramani <shravankr@nvidia.com>,
	<platform-driver-x86@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: [PATCH v3 0/3] Updates to Mellanox PMC driver
Date: Fri, 1 Sep 2023 01:43:05 -0400	[thread overview]
Message-ID: <cover.1693545970.git.shravankr@nvidia.com> (raw)

This submission consists of 3 patches:
1. Patch 1 replaces sprintf usage with snprintf or sysfs_emit, as applicable.
2. Patch 2 fixes a bug with reading unprogrammed events.
3. Patch 3 adds support for BlueField-3 platform which uses a different
access mechanism.

Patch 3:
v1 -> v2
1. Fixed naming inconsistency with events struct
2. Replaced switch case instance with if else as suggested
3. Used rounddown instead of calculating the value

v2 -> v3
Removed empty lines and added Reviewed-by tag

Shravan Kumar Ramani (3):
  platform/mellanox: mlxbf-pmc: Fix potential buffer overflows
  platform/mellanox: mlxbf-pmc: Fix reading of unprogrammed events
  platform/mellanox: mlxbf-pmc: Add support for BlueField-3

 drivers/platform/mellanox/mlxbf-pmc.c | 726 +++++++++++++++++++++++---
 1 file changed, 667 insertions(+), 59 deletions(-)

-- 
2.30.1


             reply	other threads:[~2023-09-01  5:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01  5:43 Shravan Kumar Ramani [this message]
2023-09-01  5:43 ` [PATCH v3 1/3] platform/mellanox: mlxbf-pmc: Fix potential buffer overflows Shravan Kumar Ramani
2023-09-01  5:43 ` [PATCH v3 2/3] platform/mellanox: mlxbf-pmc: Fix reading of unprogrammed events Shravan Kumar Ramani
2023-09-01  5:43 ` [PATCH v3 3/3] platform/mellanox: mlxbf-pmc: Add support for BlueField-3 Shravan Kumar Ramani
2023-09-01 10:37   ` Ilpo Järvinen
2023-09-01 10:50   ` Ilpo Järvinen

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=cover.1693545970.git.shravankr@nvidia.com \
    --to=shravankr@nvidia.com \
    --cc=davthompson@nvidia.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markgross@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --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 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.