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

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

To: Christoph Hellwig <hch@xxxxxx>
Subject: Re: [PATCH][next] nvmet: fix comparison of a u16 with -1
From: Chaitanya Kulkarni <Chaitanya.Kulkarni@xxxxxxx>
Date: Mon, 17 Dec 2018 18:04:44 +0000
Accept-language: en-US
Cc: Sagi Grimberg <sagi@xxxxxxxxxxx>, "linux-nvme@xxxxxxxxxxxxxxxxxxx" <linux-nvme@xxxxxxxxxxxxxxxxxxx>, "kernel-janitors@xxxxxxxxxxxxxxx" <kernel-janitors@xxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <20181216162638.GB12651@lst.de>
References: <20181214183121.17445-1-colin.king@canonical.com> <20181216162638.GB12651@lst.de>
User-agent: Microsoft-MacOutlook/10.13.0.181109
Wdcipoutbound: EOP-TRUE

Will send out a path.

On 12/16/18, 8:26 AM, "Christoph Hellwig" <hch@xxxxxx> wrote:

    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?

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

Prev by Date: Re: [PATCH -next] scsi: target/core: Use kmem_cache_free() instead of kfree()
Next by Date: RE: [patch] ia64: pci: Fix a condition in pcibr_dmamap_ate32()
Previous by thread: Re: [PATCH][next] nvmet: fix comparison of a u16 with -1
Next by thread: [PATCH -next] btrfs: remove set but not used variable 'num_pages'
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