public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jack Vogel <jack.vogel@oracle.com>
Cc: mustafa.ismail@intel.com, shiraz.saleem@intel.com,
	linux-rdma@vger.kernel.org
Subject: Re: [PATCH] RDMA/irdma: Move variable into switch case
Date: Wed, 1 Feb 2023 12:11:18 +0200	[thread overview]
Message-ID: <Y9o6xnalM+R4DE3D@unreal> (raw)
In-Reply-To: <20230201012823.105150-1-jack.vogel@oracle.com>

On Tue, Jan 31, 2023 at 05:28:23PM -0800, Jack Vogel wrote:
> Fix build warnings when CONFIG_INIT_STACK_ALL_ZERO is enabled.

Which warnings do you see? What is you compiler version?

The code is perfectly fine.

> 
> Signed-off-by: Jack Vogel <jack.vogel@oracle.com>
> ---
>  drivers/infiniband/hw/irdma/hw.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/infiniband/hw/irdma/hw.c b/drivers/infiniband/hw/irdma/hw.c
> index ab246447520b..e3c639a0d920 100644
> --- a/drivers/infiniband/hw/irdma/hw.c
> +++ b/drivers/infiniband/hw/irdma/hw.c
> @@ -272,8 +272,8 @@ static void irdma_process_aeq(struct irdma_pci_f *rf)
>  		}
>  
>  		switch (info->ae_id) {
> +		case IRDMA_AE_LLP_CONNECTION_ESTABLISHED: {
>  			struct irdma_cm_node *cm_node;
> -		case IRDMA_AE_LLP_CONNECTION_ESTABLISHED:
>  			cm_node = iwqp->cm_node;
>  			if (cm_node->accept_pend) {
>  				atomic_dec(&cm_node->listener->pend_accepts_cnt);
> @@ -281,7 +281,7 @@ static void irdma_process_aeq(struct irdma_pci_f *rf)
>  			}
>  			iwqp->rts_ae_rcvd = 1;
>  			wake_up_interruptible(&iwqp->waitq);
> -			break;
> +		} break;
>  		case IRDMA_AE_LLP_FIN_RECEIVED:
>  		case IRDMA_AE_RDMAP_ROE_BAD_LLP_CLOSE:
>  			if (qp->term_flags)
> -- 
> 2.39.1
> 

  reply	other threads:[~2023-02-01 10:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01  1:28 [PATCH] RDMA/irdma: Move variable into switch case Jack Vogel
2023-02-01 10:11 ` Leon Romanovsky [this message]
2023-02-02  0:09   ` Jack Vogel
2023-02-02  7:58     ` Leon Romanovsky
2023-02-03 14:44       ` Jason Gunthorpe

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=Y9o6xnalM+R4DE3D@unreal \
    --to=leon@kernel.org \
    --cc=jack.vogel@oracle.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mustafa.ismail@intel.com \
    --cc=shiraz.saleem@intel.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