nvme: pci: Fix queue_count parameter
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | nvme: pci: Return -EINVAL if given nr_queue larger than nr_cpudrivers/ | +1 | 1 reply | |
| 1/2 | nvme: pci: Return -EINVAL if given nr_queue larger than nr_cpu | +0 | 0 replies | |
| 2/2 | nvme: pci: Do not initialize local_vardrivers/ | +1 | 2 replies | |
| 2/2 | nvme: pci: Do not initialize local_var | +0 | 0 replies | |
| 2/2 | nvme: pci: Do not initialize local_var | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] nvme: pci: Fix queue_count parameter
The first patch will make it return an error if given value is larger than number of possible cpus. It has not been doing anything about it.
The second patch is just a nit for clean-up of local variable. It does not need to be initialized in this scope because kstrtoint() will return an error if it fails without referring local variable after it.
It has been reported:
http://lists.infradead.org/pipermail/linux-nvme/2019-April/023333.html
Minwoo Im (2):
nvme: pci: Return -EINVAL if given nr_queue larger than nr_cpu
nvme: pci: Do not initialize local_var
drivers/nvme/host/pci.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Signature · 1 line
2.17.1