On Thu, May 03, 2018 at 09:53:58AM +0200, Jan Kiszka wrote: > On 2018-05-02 14:39, Christoph Hellwig wrote: > > On Mon, Apr 30, 2018 at 07:48:42AM +0200, Jan Kiszka wrote: > >> From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx> > >> > >> There are no in-tree users remaining, all are converted to the managed > >> variant. And it is unlikely that any out-of-tree user got the resource > >> management right as well. So deprecate the interface and push users to > >> the managed version instead. > >> > >> To avoid raising a warning when exporting a deprecated symbol, wrap the > >> API with an inline and export an internal name. > > > > Don't deprecated it, just remove it. > > I see a clear favorite now: consider this patch obsolete. I'll send a > separate removal patch, or a v3 of this series when otherwise needed. Can you just send an update to this patch to remove it? I've got these on a branch and will just update my branch with the removal. Then I'll coordinate with Lorenzo and make sure the dependency issue is resolved.