Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031464AbdDTKWb (ORCPT ); Thu, 20 Apr 2017 06:22:31 -0400 Received: from mail-wr0-f193.google.com ([209.85.128.193]:36074 "EHLO mail-wr0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761595AbdDTKW3 (ORCPT ); Thu, 20 Apr 2017 06:22:29 -0400 Subject: Re: [PATCH v8] nvme: improve performance for virtual NVMe devices To: Keith Busch , Helen Koike References: <20170331070128.GA28852@infradead.org> <1491839467-11008-1-git-send-email-helen.koike@collabora.com> <9a406abf-1f39-003d-2863-144c4a263604@collabora.com> <20170417230140.GA16224@localhost.localdomain> Cc: Christoph Hellwig , fes@google.com, axboe@fb.com, rlnelson@google.com, "open list : NVM EXPRESS DRIVER" , mikew@google.com, digitaleric@google.com, monish@google.com, "james_p_freyensee @ linux . intel . com" , tytso@mit.edu, mlin@kernel.org, linux-kernel@vger.kernel.org From: Sagi Grimberg Message-ID: <3615ff57-543d-6e51-6eea-a9e981036446@grimberg.me> Date: Thu, 20 Apr 2017 13:22:24 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <20170417230140.GA16224@localhost.localdomain> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 649 Lines: 21 >> + Add missing maintainers from scripts/get_maintainer.pl in the email thread >> >> Hi, >> >> I would like to know if it would be possible to get this patch for kernel >> 4.12. >> Should I send a pull request? Or do you usually get the patch from the email >> thread? > > Hi Helen, > > This looks good to me. I pulled this into a branch for the next merge > window here: > > http://git.infradead.org/nvme.git/shortlog/refs/heads/for-next > > There's only one other commit at the moment in addition to yours, so > I'll just need to make sure we've got everything we want for 4.12 before > submitting our next pull request. I'm fine with this too.