1. 06 4月, 2018 1 次提交
    • R
      headers: untangle kmemleak.h from mm.h · 514c6032
      Randy Dunlap 提交于
      Currently <linux/slab.h> #includes <linux/kmemleak.h> for no obvious
      reason.  It looks like it's only a convenience, so remove kmemleak.h
      from slab.h and add <linux/kmemleak.h> to any users of kmemleak_* that
      don't already #include it.  Also remove <linux/kmemleak.h> from source
      files that do not use it.
      
      This is tested on i386 allmodconfig and x86_64 allmodconfig.  It would
      be good to run it through the 0day bot for other $ARCHes.  I have
      neither the horsepower nor the storage space for the other $ARCHes.
      
      Update: This patch has been extensively build-tested by both the 0day
      bot & kisskb/ozlabs build farms.  Both of them reported 2 build failures
      for which patches are included here (in v2).
      
      [ slab.h is the second most used header file after module.h; kernel.h is
        right there with slab.h. There could be some minor error in the
        counting due to some #includes having comments after them and I didn't
        combine all of those. ]
      
      [akpm@linux-foundation.org: security/keys/big_key.c needs vmalloc.h, per sfr]
      Link: http://lkml.kernel.org/r/e4309f98-3749-93e1-4bb7-d9501a39d015@infradead.org
      Link: http://kisskb.ellerman.id.au/kisskb/head/13396/Signed-off-by: NRandy Dunlap <rdunlap@infradead.org>
      Reviewed-by: NIngo Molnar <mingo@kernel.org>
      Reported-by: Michael Ellerman <mpe@ellerman.id.au>	[2 build failures]
      Reported-by: Fengguang Wu <fengguang.wu@intel.com>	[2 build failures]
      Reviewed-by: NAndrew Morton <akpm@linux-foundation.org>
      Cc: Wei Yongjun <weiyongjun1@huawei.com>
      Cc: Luis R. Rodriguez <mcgrof@kernel.org>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>
      Cc: John Johansen <john.johansen@canonical.com>
      Cc: Stephen Rothwell <sfr@canb.auug.org.au>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      514c6032
  2. 13 2月, 2018 1 次提交
  3. 17 1月, 2018 2 次提交
    • R
      iommu: Clean up of_iommu_init_fn · b0c560f7
      Robin Murphy 提交于
      Now that no more drivers rely on arbitrary early initialisation via an
      of_iommu_init_fn hook, let's clean up the redundant remnants. The
      IOMMU_OF_DECLARE() macro needs to remain for now, as the probe-deferral
      mechanism has no other nice way to detect built-in drivers before they
      have registered themselves, such that it can make the right decision.
      Reviewed-by: NSricharan R <sricharan@codeaurora.org>
      Signed-off-by: NRobin Murphy <robin.murphy@arm.com>
      Signed-off-by: NJoerg Roedel <jroedel@suse.de>
      b0c560f7
    • R
      iommu/exynos: Don't unconditionally steal bus ops · dc98b848
      Robin Murphy 提交于
      Removing the early device registration hook overlooked the fact that
      it only ran conditionally on a compatible device being present in the
      DT. With exynos_iommu_init() now running as an unconditional initcall,
      problems arise on non-Exynos systems when other IOMMU drivers find
      themselves unable to install their ops on the platform bus, or at worst
      the Exynos ops get called with someone else's domain and all hell breaks
      loose.
      
      The global ops/cache setup could probably all now be triggered from the
      first IOMMU probe, as with dma_dev assigment, but for the time being the
      simplest fix is to resurrect the logic from commit a7b67cd5
      ("iommu/exynos: Play nice in multi-platform builds") to explicitly check
      the DT for the presence of an Exynos IOMMU before trying anything.
      
      Fixes: 928055a0 ("iommu/exynos: Remove custom platform device registration code")
      Signed-off-by: NRobin Murphy <robin.murphy@arm.com>
      Acked-by: NMarek Szyprowski <m.szyprowski@samsung.com>
      Signed-off-by: NJoerg Roedel <jroedel@suse.de>
      dc98b848
  4. 12 10月, 2017 1 次提交
  5. 19 9月, 2017 1 次提交
  6. 30 8月, 2017 1 次提交
  7. 04 8月, 2017 2 次提交
  8. 26 7月, 2017 1 次提交
  9. 24 3月, 2017 2 次提交
  10. 22 3月, 2017 2 次提交
  11. 10 2月, 2017 2 次提交
  12. 27 1月, 2017 1 次提交
  13. 10 1月, 2017 4 次提交
  14. 15 11月, 2016 7 次提交
  15. 14 11月, 2016 1 次提交
  16. 09 8月, 2016 1 次提交
  17. 21 6月, 2016 1 次提交
  18. 15 6月, 2016 5 次提交
  19. 29 2月, 2016 2 次提交
  20. 25 2月, 2016 2 次提交