From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <keith.busch@intel.com>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fixes for 4.18
Date: Fri, 8 Jun 2018 12:51:55 -0600 [thread overview]
Message-ID: <059df767-07b1-4c8a-e084-d61bad810ba1@kernel.dk> (raw)
In-Reply-To: <8fdcff52-a017-11ba-2ec1-2d2dc265d2a8@kernel.dk>
On 6/8/18 7:09 AM, Jens Axboe wrote:
> On 6/7/18 11:58 PM, Christoph Hellwig wrote:
>> Hi Jens,
>>
>> a few more small fixes for NVMe for this merge window:
>>
>> The following changes since commit af6c5d5e01ad9f2c9ca38cccaae6b5d67ddd241f:
>>
>> Merge branch 'for-4.18' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq (2018-06-05 17:31:33 -0700)
>>
>> are available in the Git repository at:
>>
>> git://git.infradead.org/nvme.git nvme-4.18
>
> This is based off some random point in master, 2k commits or so ahead
> of my for-linus branch.
>
> The patches look fine, but I don't want to pull that. I can either apply
> the patches (trivial), or you can rebase. I'm fine with either.
JFYI, to avoid holding them up any further, I've committed them
manually and pushed it out.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: axboe@kernel.dk (Jens Axboe)
Subject: [GIT PULL] nvme fixes for 4.18
Date: Fri, 8 Jun 2018 12:51:55 -0600 [thread overview]
Message-ID: <059df767-07b1-4c8a-e084-d61bad810ba1@kernel.dk> (raw)
In-Reply-To: <8fdcff52-a017-11ba-2ec1-2d2dc265d2a8@kernel.dk>
On 6/8/18 7:09 AM, Jens Axboe wrote:
> On 6/7/18 11:58 PM, Christoph Hellwig wrote:
>> Hi Jens,
>>
>> a few more small fixes for NVMe for this merge window:
>>
>> The following changes since commit af6c5d5e01ad9f2c9ca38cccaae6b5d67ddd241f:
>>
>> Merge branch 'for-4.18' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq (2018-06-05 17:31:33 -0700)
>>
>> are available in the Git repository at:
>>
>> git://git.infradead.org/nvme.git nvme-4.18
>
> This is based off some random point in master, 2k commits or so ahead
> of my for-linus branch.
>
> The patches look fine, but I don't want to pull that. I can either apply
> the patches (trivial), or you can rebase. I'm fine with either.
JFYI, to avoid holding them up any further, I've committed them
manually and pushed it out.
--
Jens Axboe
next prev parent reply other threads:[~2018-06-08 18:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 5:58 [GIT PULL] nvme fixes for 4.18 Christoph Hellwig
2018-06-08 5:58 ` Christoph Hellwig
2018-06-08 13:09 ` Jens Axboe
2018-06-08 13:09 ` Jens Axboe
2018-06-08 18:51 ` Jens Axboe [this message]
2018-06-08 18:51 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2018-06-15 13:13 Christoph Hellwig
2018-06-15 13:13 ` Christoph Hellwig
2018-06-15 14:16 ` Jens Axboe
2018-06-15 14:16 ` Jens Axboe
2018-06-22 13:00 Christoph Hellwig
2018-06-22 13:00 ` Christoph Hellwig
2018-06-22 14:46 ` Jens Axboe
2018-06-22 14:46 ` Jens Axboe
2018-07-26 14:16 Christoph Hellwig
2018-07-26 14:16 ` Christoph Hellwig
2018-07-26 17:49 ` Jens Axboe
2018-07-26 17:49 ` Jens Axboe
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=059df767-07b1-4c8a-e084-d61bad810ba1@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--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 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.