linux-kernel - Re: [PATCH v6 0/5] prerequisites for device reserved local mem rework

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190523070755.GA23832@kroah.com>
Date:   Thu, 23 May 2019 09:07:55 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Christoph Hellwig <hch@....de>
Cc:     laurentiu.tudor@....com, stern@...land.harvard.edu,
        linux-usb@...r.kernel.org, marex@...x.de, leoyang.li@....com,
        linux-kernel@...r.kernel.org, robin.murphy@....com,
        noring@...rew.org, JuergenUrban@....de
Subject: Re: [PATCH v6 0/5] prerequisites for device reserved local mem rework

On Thu, May 23, 2019 at 08:56:02AM +0200, Christoph Hellwig wrote:
> As we seem to be getting ready to merge this series:  can the usb
> maintainers please commit it to an immutable branch that I can pull
> into the dma-mapping tree?  These changes are a preparation for
> reworking the per-device DMA coherent allocator, and I'd prefer not
> to wait for the next merge window with the next steps.

I have no objection for you just taking this whole series as-is, no need
to worry about merge conflicts with the USB tree, I doubt anything will
be touching this area of code anytime soon.

So if you want to take it now, feel free to add:

Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>

to all of these.

Or, if you really like/want a branch to pull from, I can do that as
well, which ever is easiest for you to work with as you all are doing
the hard work here, not me :)

thanks,

greg k-h