backports: revert remove_proc_subtree() for backport
authorLuis R. Rodriguez <mcgrof@do-not-panic.com>
Thu, 16 May 2013 08:23:27 +0000 (01:23 -0700)
committerJohannes Berg <johannes.berg@intel.com>
Fri, 17 May 2013 12:05:47 +0000 (14:05 +0200)
commit1caa4eac149c68c0ba1fa0ee4b2cff58c15fc272
tree5cf93109416cdf3ebe9633c412e182053b724903
parent33c4d21e3212eae28901a1c10f0f26c63c689089
backports: revert remove_proc_subtree() for backport

Intorduced in next-20130429 and Linus has merged it
onto v3.10-rc1. We cannot backport remove_proc_subtree()
modularly [0] so just go ahead and revert this change.

The alternative is to go and review each procfs usage
for each driver we have issues and see if it makes
sense to replace procs with debugfs upstream.

commit 8ce584c7416d8a85a6f3edc17d1cddefe331e87e
Author: Al Viro <viro@zeniv.linux.org.uk>
Date:   Sat Mar 30 20:13:46 2013 -0400

    procfs: add proc_remove_subtree()

    just what it sounds like; do that only to procfs subtrees you've
    created - doing that to something shared with another driver is
    not only antisocial, but might cause interesting races with
    proc_create() and its ilk.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
[0] http://marc.info/?t=136841961600002&r=1&w=2

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
patches/collateral-evolutions/drm/12-revert-remove_proc_subtree/INFO [new file with mode: 0644]
patches/collateral-evolutions/drm/12-revert-remove_proc_subtree/drivers_gpu_drm_drm_proc.patch [new file with mode: 0644]