[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a3fsDRsZh--vn4SWA-NfeeSpzueqGDvjF5jDSZ91P9+Hw@mail.gmail.com>
Date: Wed, 18 Dec 2019 18:24:32 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Jens Axboe <axboe@...nel.dk>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>
Cc: linux-scsi <linux-scsi@...r.kernel.org>,
linux-block <linux-block@...r.kernel.org>,
y2038 Mailman List <y2038@...ts.linaro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Christoph Hellwig <hch@....de>,
Ben Hutchings <ben.hutchings@...ethink.co.uk>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
Jonathan Corbet <corbet@....net>,
Al Viro <viro@...iv.linux.org.uk>,
Linux FS-devel Mailing List <linux-fsdevel@...r.kernel.org>
Subject: Re: [GIT PULL v2 00/27] block, scsi: final compat_ioctl cleanup
On Tue, Dec 17, 2019 at 11:17 PM Arnd Bergmann <arnd@...db.de> wrote:
> My plan was originally to keep the SCSI and block parts separate.
> This did not work easily because of interdependencies: I cannot
> do the final SCSI cleanup in a good way without first addressing the
> CDROM ioctls, so this is one series that I hope could be merged through
> either the block or the scsi git trees, or possibly both if you can
> pull in the same branch.
I have included the branch in my y2038 branch now, it should show up
in the following linux-next snapshots, but I'm still hoping for the block
or scsi maintainers to merge the pull request into their trees for v5.6
Jens, James, Martin:
Any suggestion for how this should be merged?
Arnd
Powered by blists - more mailing lists