[PATCH 00/17] gpio: remove unnecessary OOM messages

[Jingoo Han <jg1.han@xxxxxxxxxxx>]

The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message. For example,
k.alloc and v.alloc failures use dump_stack().

Jingoo Han (17):
      gpio: adp5520: remove unnecessary OOM messages
      gpio: adp5588: remove unnecessary OOM messages
      gpio: davinci: remove unnecessary OOM messages
      gpio: em: remove unnecessary OOM messages
      gpio: janz-ttl: remove unnecessary OOM messages
      gpio: lynxpoint: remove unnecessary OOM messages
      gpio: moxart: remove unnecessary OOM messages
      gpio: mvebu: remove unnecessary OOM messages
      gpio: palmas: remove unnecessary OOM messages
      gpio: rc5t583: remove unnecessary OOM messages
      gpio: rcar: remove unnecessary OOM messages
      gpio: rdc321x: remove unnecessary OOM messages
      gpio: SPEAr: remove unnecessary OOM messages
      gpio: tegra: remove unnecessary OOM messages
      gpio: tps6586x: remove unnecessary OOM messages
      gpio: tps65910: remove unnecessary OOM messages
      gpio: zevio: remove unnecessary OOM messages
---
 drivers/gpio/gpio-adp5520.c     |    4 +---
 drivers/gpio/gpio-adp5588.c     |    4 +---
 drivers/gpio/gpio-davinci.c     |    4 +---
 drivers/gpio/gpio-em.c          |    1 -
 drivers/gpio/gpio-janz-ttl.c    |    1 -
 drivers/gpio/gpio-lynxpoint.c   |    4 +---
 drivers/gpio/gpio-moxart.c      |    4 +---
 drivers/gpio/gpio-mvebu.c       |    4 +---
 drivers/gpio/gpio-palmas.c      |    4 +---
 drivers/gpio/gpio-rc5t583.c     |    4 +---
 drivers/gpio/gpio-rcar.c        |    1 -
 drivers/gpio/gpio-rdc321x.c     |    4 +---
 drivers/gpio/gpio-spear-spics.c |    4 +---
 drivers/gpio/gpio-tegra.c       |    4 +---
 drivers/gpio/gpio-tps6586x.c    |    4 +---
 drivers/gpio/gpio-tps65910.c    |    4 +---
 drivers/gpio/gpio-zevio.c       |    4 +---
 17 files changed, 14 insertions(+), 45 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html