public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: keith.busch@intel.com, linux-block@vger.kernel.org,
	sagi@grimberg.me, linux-nvme@lists.infradead.org
Subject: Re: two more nvme fixes for Linux 4.15
Date: Wed, 17 Jan 2018 14:05:49 -0700	[thread overview]
Message-ID: <59d8ee6a-d70d-41bd-5379-9423744f0e3f@kernel.dk> (raw)
In-Reply-To: <20180117210438.3778-1-hch@lst.de>

On 1/17/18 2:04 PM, Christoph Hellwig wrote:
> Hi Jens,
> 
> below are the two fixes for the new SGL support in 4.15 as a patch
> series due to the issues with the git server.

Applied, thanks.

-- 
Jens Axboe

      parent reply	other threads:[~2018-01-17 21:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 21:04 two more nvme fixes for Linux 4.15 Christoph Hellwig
2018-01-17 21:04 ` [PATCH 1/2] nvme-pci: check segement valid for SGL use Christoph Hellwig
2018-01-17 21:04 ` [PATCH 2/2] nvme-pci: take sglist coalescing in dma_map_sg into account Christoph Hellwig
2018-01-17 21:05 ` Jens Axboe [this message]

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=59d8ee6a-d70d-41bd-5379-9423744f0e3f@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=keith.busch@intel.com \
    --cc=linux-block@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox