All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "kbusch@kernel.org" <kbusch@kernel.org>,
	"sagi@grimberg.me" <sagi@grimberg.me>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH 0/4] nvme: code cleanup and type fixes
Date: Wed, 3 Jun 2020 22:31:08 +0000	[thread overview]
Message-ID: <BYAPR04MB4965FC25A317331BE29B98FB86880@BYAPR04MB4965.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20200603130957.GC13511@lst.de

On 6/3/20 6:10 AM, Christoph Hellwig wrote:
> We're done with the 5.8 merge window.  That being said the cleanups look
> ok and they can go into the 5.9 tree.

Sorry my bad. I didn't send this seres in time, thanks.

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

  reply	other threads:[~2020-06-03 22:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02  2:41 [PATCH 0/4] nvme: code cleanup and type fixes Chaitanya Kulkarni
2020-06-02  2:41 ` [PATCH 1/4] nvme-core: use u16 type for direcives Chaitanya Kulkarni
2020-06-03 21:07   ` Sagi Grimberg
2020-06-02  2:41 ` [PATCH 2/4] nvme-core: use u16 type for ctrl->sqsize Chaitanya Kulkarni
2020-06-03 21:07   ` Sagi Grimberg
2020-06-02  2:41 ` [PATCH 3/4] nvme-pci: use unsigned for io queue depth Chaitanya Kulkarni
2020-06-03 21:07   ` Sagi Grimberg
2020-06-02  2:41 ` [PATCH 4/4] nvme-pci: code cleanup for nvme_alloc_host_mem() Chaitanya Kulkarni
2020-06-03 21:07   ` Sagi Grimberg
2020-06-03 13:09 ` [PATCH 0/4] nvme: code cleanup and type fixes Christoph Hellwig
2020-06-03 22:31   ` Chaitanya Kulkarni [this message]
2020-06-09 13:52 ` 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=BYAPR04MB4965FC25A317331BE29B98FB86880@BYAPR04MB4965.namprd04.prod.outlook.com \
    --to=chaitanya.kulkarni@wdc.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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.