All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org,
	andrew.gospodarek@broadcom.com, selvin.xavier@broadcom.com,
	Shravya KN <shravya.k-n@broadcom.com>,
	Saravanan Vajravel <saravanan.vajravel@broadcom.com>
Subject: Re: [PATCH rdma-next 2/3] RDMA/bnxt_re: Support 2G message size
Date: Sun, 6 Jul 2025 10:37:29 +0300	[thread overview]
Message-ID: <20250706073729.GR6278@unreal> (raw)
In-Reply-To: <20250704043857.19158-3-kalesh-anakkur.purayil@broadcom.com>

On Fri, Jul 04, 2025 at 10:08:56AM +0530, Kalesh AP wrote:
> From: Selvin Xavier <selvin.xavier@broadcom.com>
> 
> bnxt_qplib_put_sges is calculating the length in
> a signed int. So handling the 2G message size
> is not working since it is considered as negative.
> 
> Use a unsigned number to calculate the total message
> length. As per the spec, IB message size shall be
> between zero and 2^31 bytes (inclusive). So adding
> a check for 2G message size.

You can easily use opto 80 chars per-line in commit messages, there is
no need to limit yourself to 50 chars.

Thanks

  reply	other threads:[~2025-07-06  7:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-04  4:38 [PATCH rdma-next 0/3] bnxt_re driver update Kalesh AP
2025-07-04  4:38 ` [PATCH rdma-next 1/3] RDMA/bnxt_re: Fix size of uverbs_copy_to() in BNXT_RE_METHOD_GET_TOGGLE_MEM Kalesh AP
2025-07-04  4:38 ` [PATCH rdma-next 2/3] RDMA/bnxt_re: Support 2G message size Kalesh AP
2025-07-06  7:37   ` Leon Romanovsky [this message]
2025-07-07  2:34     ` Kalesh Anakkur Purayil
2025-07-04  4:38 ` [PATCH rdma-next 3/3] RDMA/bnxt_re: Use macro instead of hard coded value Kalesh AP
2025-07-06  7:38 ` [PATCH rdma-next 0/3] bnxt_re driver update Leon Romanovsky

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=20250706073729.GR6278@unreal \
    --to=leon@kernel.org \
    --cc=andrew.gospodarek@broadcom.com \
    --cc=jgg@ziepe.ca \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=saravanan.vajravel@broadcom.com \
    --cc=selvin.xavier@broadcom.com \
    --cc=shravya.k-n@broadcom.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.