| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 30 Sep 2022 09:59:21 -0600
From: Keith Busch <kbusch@...nel.org>
To: "Michael Kelley (LINUX)" <mikelley@...rosoft.com>
Cc: Christoph Hellwig <hch@....de>, "axboe@...com" <axboe@...com>,
"sagi@...mberg.me" <sagi@...mberg.me>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] nvme: Fix IOC_PR_CLEAR and IOC_PR_RELEASE ioctls for
nvme devices
On Fri, Sep 30, 2022 at 03:47:48PM +0000, Michael Kelley (LINUX) wrote:
> From: Christoph Hellwig <hch@....de> Sent: Tuesday, September 27, 2022 12:21 AM
> > To: Michael Kelley (LINUX) <mikelley@...rosoft.com>
> > Cc: kbusch@...nel.org; axboe@...com; hch@....de; sagi@...mberg.me; linux-
> > nvme@...ts.infradead.org; linux-kernel@...r.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
Powered by blists - more mailing lists