From: Jason Gunthorpe <jgg@nvidia.com>
To: Selvin Xavier <selvin.xavier@broadcom.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org,
andrew.gospodarek@broadcom.com
Subject: Re: [PATCH for-next 0/7] RDMA/bnxt_re: driver updates
Date: Fri, 19 May 2023 15:15:02 -0300 [thread overview]
Message-ID: <ZGe8pqKfW33/sQUd@nvidia.com> (raw)
In-Reply-To: <1684478897-12247-1-git-send-email-selvin.xavier@broadcom.com>
On Thu, May 18, 2023 at 11:48:10PM -0700, Selvin Xavier wrote:
> Includes some of the generic fixes/update to bnxt_re driver.
> Please review and apply.
>
> Thanks,
> Selvin
>
> Kalesh AP (6):
> RDMA/bnxt_re: Fix to remove unnecessary return labels
> RDMA/bnxt_re: Use unique names while registering interrupts
> RDMA/bnxt_re: Remove a redundant check inside bnxt_re_update_gid
> RDMA/bnxt_re: Fix to remove an unnecessary log
> RDMA/bnxt_re: Return directly without goto jumps
> RDMA/bnxt_re: Remove unnecessary checks
>
> Selvin Xavier (1):
> RDMA/bnxt_re: Disable/kill tasklet only if it is enabled
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2023-05-19 18:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 6:48 [PATCH for-next 0/7] RDMA/bnxt_re: driver updates Selvin Xavier
2023-05-19 6:48 ` [PATCH for-next 1/7] RDMA/bnxt_re: Disable/kill tasklet only if it is enabled Selvin Xavier
2023-05-19 6:48 ` [PATCH for-next 2/7] RDMA/bnxt_re: Fix to remove unnecessary return labels Selvin Xavier
2023-05-19 6:48 ` [PATCH for-next 3/7] RDMA/bnxt_re: Use unique names while registering interrupts Selvin Xavier
2023-05-19 6:48 ` [PATCH for-next 4/7] RDMA/bnxt_re: Remove a redundant check inside bnxt_re_update_gid Selvin Xavier
2023-05-19 6:48 ` [PATCH for-next 5/7] RDMA/bnxt_re: Fix to remove an unnecessary log Selvin Xavier
2023-05-19 6:48 ` [PATCH for-next 6/7] RDMA/bnxt_re: Return directly without goto jumps Selvin Xavier
2023-05-19 6:48 ` [PATCH for-next 7/7] RDMA/bnxt_re: Remove unnecessary checks Selvin Xavier
2023-05-19 18:15 ` Jason Gunthorpe [this message]
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=ZGe8pqKfW33/sQUd@nvidia.com \
--to=jgg@nvidia.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=selvin.xavier@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.