From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Vadim Pasternak <vadimp@nvidia.com>
Cc: Alok Tiwari <alok.a.tiwari@oracle.com>,
"hansg@kernel.org" <hansg@kernel.org>,
David Thompson <davthompson@nvidia.com>,
Michael Shych <michaelsh@nvidia.com>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 1/2] platform/mellanox: Fix spelling and comment clarity in Mellanox drivers
Date: Wed, 25 Jun 2025 15:36:25 +0300 (EEST) [thread overview]
Message-ID: <96280bbc-c20d-430c-493b-35d883e4622d@linux.intel.com> (raw)
In-Reply-To: <PH7PR12MB66686B87D8572B5812A1402EAF78A@PH7PR12MB6668.namprd12.prod.outlook.com>
On Tue, 24 Jun 2025, Vadim Pasternak wrote:
> > -----Original Message-----
> > From: Alok Tiwari <alok.a.tiwari@oracle.com>
> > Sent: Sunday, 22 June 2025 10:29
> > To: hansg@kernel.org; ilpo.jarvinen@linux.intel.com; David Thompson
> > <davthompson@nvidia.com>; Michael Shych <michaelsh@nvidia.com>;
> > Vadim Pasternak <vadimp@nvidia.com>; platform-driver-x86@vger.kernel.org
> > Cc: alok.a.tiwari@oracle.com; linux-kernel@vger.kernel.org
> > Subject: [PATCH 1/2] platform/mellanox: Fix spelling and comment clarity in
> > Mellanox drivers
> >
> > This commit corrects several minor typographical errors in comments and
> > error messages across multiple Mellanox platform driver.
> > Fixed spelling of "thresholds", "region", "platform", "default", and removed
> > redundant spaces in comment strings and error logs.
> >
> > These changes are cosmetic and do not affect runtime behavior.
> >
> > Signed-off-by: Alok Tiwari <alok.a.tiwari@oracle.com>
>
> Reviewed-by: Vadim Pasternak <vadimp@nvidia.com>
Okay folks, this was easy to review but what about the second patch which
does a real change to code (albeit only printing related)? Could somebody
review that as well? :-)
--
i.
> > ---
> > drivers/platform/mellanox/mlxbf-tmfifo.c | 2 +-
> > drivers/platform/mellanox/mlxreg-dpu.c | 2 +-
> > drivers/platform/mellanox/mlxreg-lc.c | 10 +++++-----
> > 3 files changed, 7 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/platform/mellanox/mlxbf-tmfifo.c
> > b/drivers/platform/mellanox/mlxbf-tmfifo.c
> > index aae99adb29eb0..6264379d96907 100644
> > --- a/drivers/platform/mellanox/mlxbf-tmfifo.c
> > +++ b/drivers/platform/mellanox/mlxbf-tmfifo.c
> > @@ -1287,7 +1287,7 @@ static void mlxbf_tmfifo_get_cfg_mac(u8 *mac)
> > ether_addr_copy(mac, mlxbf_tmfifo_net_default_mac); }
> >
> > -/* Set TmFifo thresolds which is used to trigger interrupts. */
> > +/* Set TmFifo thresholds which is used to trigger interrupts. */
> > static void mlxbf_tmfifo_set_threshold(struct mlxbf_tmfifo *fifo) {
> > u64 ctl;
> > diff --git a/drivers/platform/mellanox/mlxreg-dpu.c
> > b/drivers/platform/mellanox/mlxreg-dpu.c
> > index 52260106a9f16..39f89c47144a2 100644
> > --- a/drivers/platform/mellanox/mlxreg-dpu.c
> > +++ b/drivers/platform/mellanox/mlxreg-dpu.c
> > @@ -483,7 +483,7 @@ static int mlxreg_dpu_config_init(struct mlxreg_dpu
> > *mlxreg_dpu, void *regmap,
> > mlxreg_dpu-
> > >io_data,
> > sizeof(*mlxreg_dpu-
> > >io_data));
> > if (IS_ERR(mlxreg_dpu->io_regs)) {
> > - dev_err(dev, "Failed to create regio for client %s at bus
> > %d at addr 0x%02x\n",
> > + dev_err(dev, "Failed to create region for client %s at
> > bus %d at
> > +addr 0x%02x\n",
> > data->hpdev.brdinfo->type, data->hpdev.nr,
> > data->hpdev.brdinfo->addr);
> > return PTR_ERR(mlxreg_dpu->io_regs); diff --git
> > a/drivers/platform/mellanox/mlxreg-lc.c b/drivers/platform/mellanox/mlxreg-
> > lc.c
> > index aee395bb48ae4..8eef3d990d1ae 100644
> > --- a/drivers/platform/mellanox/mlxreg-lc.c
> > +++ b/drivers/platform/mellanox/mlxreg-lc.c
> > @@ -57,9 +57,9 @@ enum mlxreg_lc_state {
> > * @dev: platform device;
> > * @lock: line card lock;
> > * @par_regmap: parent device regmap handle;
> > - * @data: pltaform core data;
> > + * @data: platform core data;
> > * @io_data: register access platform data;
> > - * @led_data: LED platform data ;
> > + * @led_data: LED platform data;
> > * @mux_data: MUX platform data;
> > * @led: LED device;
> > * @io_regs: register access device;
> > @@ -171,7 +171,7 @@ static int mlxreg_lc_chan[] = {
> > 0x4e, 0x4f
> > };
> >
> > -/* Defaul mux configuration. */
> > +/* Default mux configuration. */
> > static struct mlxcpld_mux_plat_data mlxreg_lc_mux_data[] = {
> > {
> > .chan_ids = mlxreg_lc_chan,
> > @@ -181,7 +181,7 @@ static struct mlxcpld_mux_plat_data
> > mlxreg_lc_mux_data[] = {
> > },
> > };
> >
> > -/* Defaul mux board info. */
> > +/* Default mux board info. */
> > static struct i2c_board_info mlxreg_lc_mux_brdinfo = {
> > I2C_BOARD_INFO("i2c-mux-mlxcpld", 0x32), }; @@ -758,7 +758,7
> > @@ mlxreg_lc_config_init(struct mlxreg_lc *mlxreg_lc, void *regmap,
> > platform_device_register_resndata(dev, "mlxreg-io", data-
> > >hpdev.nr, NULL, 0,
> > mlxreg_lc->io_data,
> > sizeof(*mlxreg_lc->io_data));
> > if (IS_ERR(mlxreg_lc->io_regs)) {
> > - dev_err(dev, "Failed to create regio for client %s at bus
> > %d at addr 0x%02x\n",
> > + dev_err(dev, "Failed to create region for client %s at
> > bus %d at
> > +addr 0x%02x\n",
> > data->hpdev.brdinfo->type, data->hpdev.nr,
> > data->hpdev.brdinfo->addr);
> > err = PTR_ERR(mlxreg_lc->io_regs);
> > --
> > 2.46.0
>
>
next prev parent reply other threads:[~2025-06-25 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 7:29 [PATCH 1/2] platform/mellanox: Fix spelling and comment clarity in Mellanox drivers Alok Tiwari
2025-06-22 7:29 ` [PATCH 2/2] platform/mellanox: nvsw-sn2201: Fix bus number in adapter error message Alok Tiwari
2025-06-25 18:12 ` Vadim Pasternak
2025-06-24 20:17 ` [PATCH 1/2] platform/mellanox: Fix spelling and comment clarity in Mellanox drivers David Thompson
2025-06-24 20:50 ` Vadim Pasternak
2025-06-25 12:36 ` Ilpo Järvinen [this message]
2025-06-26 15:19 ` 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=96280bbc-c20d-430c-493b-35d883e4622d@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=alok.a.tiwari@oracle.com \
--cc=davthompson@nvidia.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michaelsh@nvidia.com \
--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 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).