1. 31 8月, 2018 1 次提交
    • R
      clk: Convert to using %pOFn instead of device_node.name · e665f029
      Rob Herring 提交于
      In preparation to remove the node name pointer from struct device_node,
      convert printf users to use the %pOFn format specifier.
      
      Cc: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
      Cc: Michael Turquette <mturquette@baylibre.com>
      Cc: Stephen Boyd <sboyd@kernel.org>
      Cc: linux-clk@vger.kernel.org
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: linux-renesas-soc@vger.kernel.org
      Cc: linux-omap@vger.kernel.org
      Signed-off-by: NRob Herring <robh@kernel.org>
      Signed-off-by: NStephen Boyd <sboyd@kernel.org>
      e665f029
  2. 22 3月, 2018 1 次提交
  3. 17 3月, 2018 1 次提交
    • A
      clk: fix false-positive Wmaybe-uninitialized warning · ce33f284
      Arnd Bergmann 提交于
      When we build this driver with on x86-32, gcc produces a false-positive warning:
      
      drivers/clk/renesas/clk-sh73a0.c: In function 'sh73a0_cpg_clocks_init':
      drivers/clk/renesas/clk-sh73a0.c:155:10: error: 'parent_name' may be used uninitialized in this function [-Werror=maybe-uninitialized]
         return clk_register_fixed_factor(NULL, name, parent_name, 0,
      
      We can work around that warning by adding a fake initialization, I tried
      and failed to come up with any better workaround. This is currently one
      of few remaining warnings for a 4.14.y randconfig build, so it would be
      good to also have it backported at least to that version. Older versions
      have more randconfig warnings, so we might not care.
      
      I had not noticed this earlier, because one patch in my randconfig test
      tree removes the '-ffreestanding' option on x86-32, and that avoids
      the warning. The -ffreestanding flag was originally global but moved
      into arch/i386 by Andi Kleen in commit 6edfba1b ("[PATCH] x86_64:
      Don't define string functions to builtin") as a 'temporary workaround'.
      
      Like many temporary hacks, this turned out to be rather long-lived, from
      all I can tell we still need a simple fix to asm/string_32.h before it
      can be removed, but I'm not sure about how to best do that.
      
      Cc: stable@vger.kernel.org
      Cc: Andi Kleen <ak@linux.intel.com>
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NGeert Uytterhoeven <geert+renesas@glider.be>
      Signed-off-by: NStephen Boyd <sboyd@kernel.org>
      ce33f284
  4. 16 3月, 2016 1 次提交
  5. 04 3月, 2016 1 次提交
  6. 29 7月, 2015 1 次提交
  7. 14 1月, 2015 1 次提交
  8. 21 12月, 2014 1 次提交