From: Wolfram Sang <wsa@the-dreams.de>
To: linux-i2c@vger.kernel.org
Cc: Peter Rosin <peda@axentia.se>, Wolfram Sang <wsa@the-dreams.de>
Subject: [PATCH v2 0/2] i2c: mux: move include files out of include/linux/i2c
Date: Sun, 13 Aug 2017 15:58:54 +0200 [thread overview]
Message-ID: <20170813135856.3454-1-wsa@the-dreams.de> (raw)
include/linux/i2c is to be deprecated, so move these header files only
including platform_data to the better suited platform_data directory.
Peter, I know I said I'll include these two patches in my for-current branch.
But other of these cleanup patches missed this merge window as well. Since I
need to wait for the next merge window anyhow (until all patches are applied),
I'd think these patches can also go the proper way via your tree, too.
These patches are rebased to v4.13-rc4 (let me know if you prefer a
different base). The PCA patch has an empty line removed now.
Thanks,
Wolfram
Wolfram Sang (2):
i2c: mux: pca954x: move header file out of I2C realm
i2c: mux: mlxcpld: move header file out of I2C realm
drivers/i2c/muxes/i2c-mux-mlxcpld.c | 2 +-
drivers/i2c/muxes/i2c-mux-pca9541.c | 3 +--
drivers/i2c/muxes/i2c-mux-pca954x.c | 2 +-
include/linux/{i2c => platform_data}/pca954x.h | 0
include/linux/{i2c => platform_data/x86}/mlxcpld.h | 0
5 files changed, 3 insertions(+), 4 deletions(-)
rename include/linux/{i2c => platform_data}/pca954x.h (100%)
rename include/linux/{i2c => platform_data/x86}/mlxcpld.h (100%)
--
2.11.0
next reply other threads:[~2017-08-13 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-13 13:58 Wolfram Sang [this message]
2017-08-13 13:58 ` [PATCH v2 1/2] i2c: mux: pca954x: move header file out of I2C realm Wolfram Sang
2017-08-13 13:58 ` [PATCH v2 2/2] i2c: mux: mlxcpld: " Wolfram Sang
2017-08-13 21:23 ` [PATCH v2 0/2] i2c: mux: move include files out of include/linux/i2c Peter Rosin
2017-08-14 8:08 ` 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=20170813135856.3454-1-wsa@the-dreams.de \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--cc=peda@axentia.se \
/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).