All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Wesley Sheng <wesley.sheng@amd.com>
Cc: kbusch@kernel.org, axboe@fb.com, hch@lst.de, sagi@grimberg.me,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	logang@deltatee.com, wesleyshenggit@sina.com
Subject: Re: [PATCH] nvme.h: add missing nvme_lba_range_type endianness annotations
Date: Thu, 17 Jun 2021 15:54:46 +0200	[thread overview]
Message-ID: <20210617135446.GA28419@lst.de> (raw)
In-Reply-To: <20210616052508.78970-1-wesley.sheng@amd.com>

Thanks,

applied to nvme-5.14.

(and I hope you do not actually plan to use the horribly ill defined
LBA ranges for anything..)

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Wesley Sheng <wesley.sheng@amd.com>
Cc: kbusch@kernel.org, axboe@fb.com, hch@lst.de, sagi@grimberg.me,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	logang@deltatee.com, wesleyshenggit@sina.com
Subject: Re: [PATCH] nvme.h: add missing nvme_lba_range_type endianness annotations
Date: Thu, 17 Jun 2021 15:54:46 +0200	[thread overview]
Message-ID: <20210617135446.GA28419@lst.de> (raw)
In-Reply-To: <20210616052508.78970-1-wesley.sheng@amd.com>

Thanks,

applied to nvme-5.14.

(and I hope you do not actually plan to use the horribly ill defined
LBA ranges for anything..)

  reply	other threads:[~2021-06-17 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16  5:25 [PATCH] nvme.h: add missing nvme_lba_range_type endianness annotations Wesley Sheng
2021-06-16  5:25 ` Wesley Sheng
2021-06-17 13:54 ` Christoph Hellwig [this message]
2021-06-17 13:54   ` Christoph Hellwig

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=20210617135446.GA28419@lst.de \
    --to=hch@lst.de \
    --cc=axboe@fb.com \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=logang@deltatee.com \
    --cc=sagi@grimberg.me \
    --cc=wesley.sheng@amd.com \
    --cc=wesleyshenggit@sina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.