Re: [PATCH v2] net/mlx5e: Refactor switch statements to avoid using uninitialized variables

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v2] net/mlx5e: Refactor switch statements to avoid using uninitialized variables
From: David Miller <davem@xxxxxxxxxxxxx>
Date: Tue, 09 Jul 2019 22:36:57 -0700 (PDT)
Cc: saeedm@xxxxxxxxxxxx, leon@xxxxxxxxxx, borisp@xxxxxxxxxxxx, netdev@xxxxxxxxxxxxxxx, linux-rdma@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, clang-built-linux@xxxxxxxxxxxxxxxx, ndesaulniers@xxxxxxxxxx
In-reply-to: <20190710044748.3924-1-natechancellor@gmail.com>
References: <20190708231154.89969-1-natechancellor@gmail.com> <20190710044748.3924-1-natechancellor@gmail.com>

I applied your simpler addition of the return statement so that I could
get the net-next pull request out tonight, just FYI...

Follow-Ups:
- Re: [PATCH v2] net/mlx5e: Refactor switch statements to avoid using uninitialized variables
  - From: Nathan Chancellor

References:
- [PATCH] net/mlx5e: Return in default case statement in tx_post_resync_params
  - From: Nathan Chancellor
- [PATCH v2] net/mlx5e: Refactor switch statements to avoid using uninitialized variables
  - From: Nathan Chancellor

Prev by Date: Re: BUG: MAX_STACK_TRACE_ENTRIES too low! (2)
Next by Date: Re: [PATCH v2] net/mlx5e: Refactor switch statements to avoid using uninitialized variables
Previous by thread: Re: [PATCH v2] net/mlx5e: Refactor switch statements to avoid using uninitialized variables
Next by thread: Re: [PATCH v2] net/mlx5e: Refactor switch statements to avoid using uninitialized variables
Index(es):
- Date
- Thread

[Index of Archives] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Photo] [Yosemite News] [Yosemite Photos] [Linux Kernel] [Linux SCSI] [XFree86]

Powered by Linux