From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Jules Irenge <jbi.octave@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
markgross@kernel.org, vadimp@nvidia.com,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 2/3] platform/mellanox: mlxbf-tmfifo: Remove unnecessary bool conversion
Date: Tue, 14 Nov 2023 13:09:15 +0200 (EET) [thread overview]
Message-ID: <42dad56-f73a-cfcf-eedb-60412eb6a7e4@linux.intel.com> (raw)
In-Reply-To: <ZUWIIKbz4vukl8qb@octinomon>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
On Fri, 3 Nov 2023, Jules Irenge wrote:
> This commit fixes coccinelle warning in macro function
> IS_VRING_DROP() which complains conversion to bool not needed here.
>
> Signed-off-by: Jules Irenge <jbi.octave@gmail.com>
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Not an end of the world but just in case you have it stored somewhere, my
email address was lacking the first letter in your post.
--
i.
> ---
> drivers/platform/mellanox/mlxbf-tmfifo.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/platform/mellanox/mlxbf-tmfifo.c b/drivers/platform/mellanox/mlxbf-tmfifo.c
> index ab7d7a1235b8..88472c024680 100644
> --- a/drivers/platform/mellanox/mlxbf-tmfifo.c
> +++ b/drivers/platform/mellanox/mlxbf-tmfifo.c
> @@ -91,7 +91,7 @@ struct mlxbf_tmfifo_vring {
> /* Check whether vring is in drop mode. */
> #define IS_VRING_DROP(_r) ({ \
> typeof(_r) (r) = (_r); \
> - (r->desc_head == &r->drop_desc ? true : false); })
> + r->desc_head == &r->drop_desc; })
>
> /* A stub length to drop maximum length packet. */
> #define VRING_DROP_DESC_MAX_LEN GENMASK(15, 0)
>
next prev parent reply other threads:[~2023-11-14 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 23:54 [PATCH 2/3] platform/mellanox: mlxbf-tmfifo: Remove unnecessary bool conversion Jules Irenge
2023-11-14 11:09 ` Ilpo Järvinen [this message]
2023-11-14 11:11 ` Ilpo Järvinen
2023-11-14 11:46 ` Jules Irenge
2023-11-20 12:03 ` Hans de Goede
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=42dad56-f73a-cfcf-eedb-60412eb6a7e4@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=jbi.octave@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox