From: Wolfram Sang <wsa@the-dreams.de>
To: linux-i2c@vger.kernel.org
Cc: Wolfram Sang <wsa@the-dreams.de>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] gpu: move include files out of include/linux/i2c
Date: Mon, 22 May 2017 00:11:13 +0200 [thread overview]
Message-ID: <20170521221114.2685-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. Please let me know if you think another
location is more suitable.
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 (1):
gpu: drm: tc35876x: move header file out of I2C realm
arch/x86/platform/intel-mid/device_libs/platform_tc35876x.c | 2 +-
drivers/gpu/drm/gma500/tc35876x-dsi-lvds.c | 2 +-
include/linux/{i2c => platform_data}/tc35876x.h | 0
3 files changed, 2 insertions(+), 2 deletions(-)
rename include/linux/{i2c => platform_data}/tc35876x.h (100%)
--
2.11.0
next reply other threads:[~2017-05-21 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 22:11 Wolfram Sang [this message]
2017-05-21 22:11 ` [PATCH 1/1] gpu: drm: tc35876x: move header file out of I2C realm Wolfram Sang
2017-06-05 21:38 ` [PATCH 0/1] gpu: move include files out of include/linux/i2c Patrik Jakobsson
2017-08-13 14:05 ` Wolfram Sang
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=20170521221114.2685-1-wsa@the-dreams.de \
--to=wsa@the-dreams.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).