linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: linux-i2c@vger.kernel.org
Cc: Wolfram Sang <wsa@the-dreams.de>,
	adi-buildroot-devel@lists.sourceforge.net,
	linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mips@linux-mips.org
Subject: [PATCH 0/3] gpio: move include files out of include/linux/i2c
Date: Sun, 21 May 2017 23:57:24 +0200	[thread overview]
Message-ID: <20170521215727.1243-1-wsa@the-dreams.de> (raw)

It doesn't make sense to use include/linux/i2c for client drivers which may in
fact rather be hwmon or input or whatever devices. As a result, I want to
deprecate include/linux/i2c for good. This series moves the include files to a
better location, largely include/linux/platform_data because that is what most
of the moved include files contain.

I prefer the series to go upstream via the subsystem tree; if you prefer that I
take it via I2C, just let me know.

No runtime testing because of no HW, but buildbot is happy with this series at
least. A branch can be found here:

git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/platform_data

Thanks and kind regards,

   Wolfram


Wolfram Sang (3):
  gpio: max732x: move header file out of I2C realm
  gpio: pcf857x: move header file out of I2C realm
  gpio: adp5588: move header file out of I2C realm

 arch/arm/mach-davinci/board-da830-evm.c        | 2 +-
 arch/arm/mach-davinci/board-dm644x-evm.c       | 2 +-
 arch/arm/mach-davinci/board-dm646x-evm.c       | 2 +-
 arch/arm/mach-pxa/balloon3.c                   | 2 +-
 arch/arm/mach-pxa/littleton.c                  | 2 +-
 arch/arm/mach-pxa/stargate2.c                  | 2 +-
 arch/blackfin/mach-bf537/boards/stamp.c        | 2 +-
 arch/mips/ath79/mach-pb44.c                    | 2 +-
 drivers/gpio/gpio-adp5588.c                    | 2 +-
 drivers/gpio/gpio-max732x.c                    | 2 +-
 drivers/gpio/gpio-pcf857x.c                    | 2 +-
 drivers/input/keyboard/adp5588-keys.c          | 2 +-
 include/linux/{i2c => platform_data}/adp5588.h | 0
 include/linux/{i2c => platform_data}/max732x.h | 0
 include/linux/{i2c => platform_data}/pcf857x.h | 0
 15 files changed, 12 insertions(+), 12 deletions(-)
 rename include/linux/{i2c => platform_data}/adp5588.h (100%)
 rename include/linux/{i2c => platform_data}/max732x.h (100%)
 rename include/linux/{i2c => platform_data}/pcf857x.h (100%)

-- 
2.11.0


             reply	other threads:[~2017-05-21 21:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-21 21:57 Wolfram Sang [this message]
2017-05-21 21:57 ` [PATCH 1/3] gpio: max732x: move header file out of I2C realm Wolfram Sang
2017-05-23  9:34   ` Linus Walleij
2017-05-21 21:57 ` [PATCH 2/3] gpio: pcf857x: " Wolfram Sang
2017-05-23  9:35   ` Linus Walleij
2017-05-25  8:52     ` Sekhar Nori
2017-05-21 21:57 ` [PATCH 3/3] gpio: adp5588: " Wolfram Sang
2017-05-22 23:40   ` Dmitry Torokhov
2017-05-25 17:09     ` Wolfram Sang
2017-05-29 11:37   ` Linus Walleij

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170521215727.1243-1-wsa@the-dreams.de \
    --to=wsa@the-dreams.de \
    --cc=adi-buildroot-devel@lists.sourceforge.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).