Re: [PATCH][next] nvmet: fix comparison of a u16 with -1

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

To: Colin King <colin.king@xxxxxxxxxxxxx>
Subject: Re: [PATCH][next] nvmet: fix comparison of a u16 with -1
From: Christoph Hellwig <hch@xxxxxx>
Date: Sun, 16 Dec 2018 17:26:38 +0100
Cc: Christoph Hellwig <hch@xxxxxx>, Sagi Grimberg <sagi@xxxxxxxxxxx>, linux-nvme@xxxxxxxxxxxxxxxxxxx, kernel-janitors@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, chaitanya.kulkarni@xxxxxxx
In-reply-to: <20181214183121.17445-1-colin.king@canonical.com>
References: <20181214183121.17445-1-colin.king@canonical.com>
User-agent: Mutt/1.5.17 (2007-11-01)

Thanks, applied.

Maybe it might be worth adding a NVME_NO_ERR_LOC defintion to clean
this up a bit more.  Chaitanya, can you look into that?

Follow-Ups:
- Re: [PATCH][next] nvmet: fix comparison of a u16 with -1
  - From: Chaitanya Kulkarni

References:
- [PATCH][next] nvmet: fix comparison of a u16 with -1
  - From: Colin King

Prev by Date: Re: [PATCH][next] nvme-tcp: fix spelling mistake "attepmpt" -> "attempt"
Next by Date: [PATCH] drm: Fix an error pointer dereference()
Previous by thread: [PATCH][next] nvmet: fix comparison of a u16 with -1
Next by thread: Re: [PATCH][next] nvmet: fix comparison of a u16 with -1
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Development] [Kernel Announce] [Kernel Newbies] [Linux Networking Development] [Share Photos] [IDE] [Security] [Git] [Netfilter] [Yosemite News] [MIPS Linux] [ARM Linux] [Device Mapper]

Powered by Linux