From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4EB42C433F5 for ; Fri, 30 Sep 2022 15:59:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231732AbiI3P73 (ORCPT ); Fri, 30 Sep 2022 11:59:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58872 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229615AbiI3P70 (ORCPT ); Fri, 30 Sep 2022 11:59:26 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D146C1739E6 for ; Fri, 30 Sep 2022 08:59:25 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 66BDA623A1 for ; Fri, 30 Sep 2022 15:59:25 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4A68BC433D6; Fri, 30 Sep 2022 15:59:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1664553564; bh=oiMIJH/YyE90Kaik4KiVIajjTIr2/v8irSkheGdEvcI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Q6VJGl/3uY+4RZD/9CcUG+zHtX+GYmeAeTjfqTQpLN3U3AD3SzvH6w6MkvcQ4LhUM rcRd6vhiK12MB8p8Yj2SFvbG9y4Pk+xe6G5e/YWA9xzLsoI1tjAP3Oy8JbvharVyxn DUGCrGaBon+uZsopwNDjtwOseNl3DXY2ya+ZcnEhlZY0silUmDRj+kfbuFsAv73TA4 DhCrUH9FmMZq7VVLGQZiFKezUvQQann7TwyOTvcJfXPQQvsQmR9C+hQIvDh5c1J4/P IfDzCX+1nwGT1dbEtbQYOi4ryaTM/eYAN2KzrDBJ74dhcO/U78sDHKnMNiaQVkzFfN +B0VD29TJGz2w== Date: Fri, 30 Sep 2022 09:59:21 -0600 From: Keith Busch To: "Michael Kelley (LINUX)" Cc: Christoph Hellwig , "axboe@fb.com" , "sagi@grimberg.me" , "linux-nvme@lists.infradead.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 1/1] nvme: Fix IOC_PR_CLEAR and IOC_PR_RELEASE ioctls for nvme devices Message-ID: References: <1663908549-118490-1-git-send-email-mikelley@microsoft.com> <20220927072101.GC16285@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 30, 2022 at 03:47:48PM +0000, Michael Kelley (LINUX) wrote: > From: Christoph Hellwig Sent: Tuesday, September 27, 2022 12:21 AM > > To: Michael Kelley (LINUX) > > Cc: kbusch@kernel.org; axboe@fb.com; hch@lst.de; sagi@grimberg.me; linux- > > nvme@lists.infradead.org; linux-kernel@vger.kernel.org > > Subject: Re: [PATCH 1/1] nvme: Fix IOC_PR_CLEAR and IOC_PR_RELEASE ioctls for > > nvme devices > > > > Thanks, > > > > applied to 6.0. > > Christoph -- where did this get applied? I'm not seeing it in either the linux > or linux-next trees. The path for nvme patches to upstream goes through the nvme tree[1] -> block tree [2], then linux mainline. The pull request from block to mainline containing your patch was sent earlier today[3], and we typically see those merged within a few hours. [1] http://git.infradead.org/nvme.git [2] https://git.kernel.dk/cgit/linux-block/ [3] https://lore.kernel.org/linux-block/e5c2a0e5-1a04-50b1-78f0-08d998a8d4e7@kernel.dk/T/#u