From: Vadim Pasternak <vadimp@nvidia.com>
To: wsa@the-dreams.de
Cc: peda@axentia.se, linux-i2c@vger.kernel.org,
Vadim Pasternak <vadimp@nvidia.com>
Subject: [Re-send: PATCH i2c-next 3/6] i2c: mux: mlxcpld: Move header file out of x86 realm
Date: Wed, 18 Nov 2020 16:44:13 +0200 [thread overview]
Message-ID: <20201118144416.184120-4-vadimp@nvidia.com> (raw)
In-Reply-To: <20201118144416.184120-1-vadimp@nvidia.com>
Move out header file from include/linux/platform_data/x86/ to
include/linux/platform_data/, since it does not depend on x86
architecture.
Signed-off-by: Vadim Pasternak <vadimp@nvidia.com>
Reviewed-by: Michael Shych <michaelsh@nvidia.com>
---
drivers/i2c/muxes/i2c-mux-mlxcpld.c | 2 +-
include/linux/platform_data/{x86 => }/mlxcpld.h | 0
2 files changed, 1 insertion(+), 1 deletion(-)
rename include/linux/platform_data/{x86 => }/mlxcpld.h (100%)
diff --git a/drivers/i2c/muxes/i2c-mux-mlxcpld.c b/drivers/i2c/muxes/i2c-mux-mlxcpld.c
index 53bce81cf5c9..3d894cfb19df 100644
--- a/drivers/i2c/muxes/i2c-mux-mlxcpld.c
+++ b/drivers/i2c/muxes/i2c-mux-mlxcpld.c
@@ -11,7 +11,7 @@
#include <linux/io.h>
#include <linux/init.h>
#include <linux/module.h>
-#include <linux/platform_data/x86/mlxcpld.h>
+#include <linux/platform_data/mlxcpld.h>
#include <linux/platform_device.h>
#include <linux/slab.h>
diff --git a/include/linux/platform_data/x86/mlxcpld.h b/include/linux/platform_data/mlxcpld.h
similarity index 100%
rename from include/linux/platform_data/x86/mlxcpld.h
rename to include/linux/platform_data/mlxcpld.h
--
2.11.0
next prev parent reply other threads:[~2020-11-18 14:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 14:44 [Re-send: PATCH i2c-next 0/6] i2c: mux: mlxcpld: Extend driver functionality and update licenses Vadim Pasternak
2020-11-18 14:44 ` [Re-send: PATCH i2c-next 1/6] i2c: mux: mlxcpld: Update module license Vadim Pasternak
2020-11-18 14:44 ` [Re-send: PATCH i2c-next 2/6] platform/x86: " Vadim Pasternak
2020-11-18 14:44 ` Vadim Pasternak [this message]
2020-11-18 14:44 ` [Re-send: PATCH i2c-next 4/6] i2c: mux: mlxcpld: Convert driver to platform driver Vadim Pasternak
2021-01-07 7:52 ` Peter Rosin
2020-11-18 14:44 ` [Re-send: PATCH i2c-next 5/6] i2c: mux: mlxcpld: Extend driver to support word address space devices Vadim Pasternak
2021-01-07 10:03 ` Peter Rosin
2021-01-07 20:43 ` Vadim Pasternak
2021-01-08 8:02 ` Peter Rosin
2021-01-11 18:11 ` Vadim Pasternak
2021-01-11 21:22 ` Peter Rosin
2021-01-11 23:24 ` Vadim Pasternak
2021-01-12 9:35 ` Peter Rosin
2021-01-12 10:11 ` wsa
2021-01-14 7:49 ` Peter Rosin
2021-01-14 18:43 ` Vadim Pasternak
2021-01-14 21:10 ` Peter Rosin
2021-01-14 21:13 ` Vadim Pasternak
2020-11-18 14:44 ` [Re-send: PATCH i2c-next 6/6] i2c: mux: mlxcpld: Extend supported mux number Vadim Pasternak
2021-01-07 10:10 ` Peter Rosin
2021-01-05 10:27 ` [Re-send: PATCH i2c-next 0/6] i2c: mux: mlxcpld: Extend driver functionality and update licenses Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2020-11-18 13:49 Vadim Pasternak
2020-11-18 13:49 ` [Re-send: PATCH i2c-next 3/6] i2c: mux: mlxcpld: Move header file out of x86 realm Vadim Pasternak
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=20201118144416.184120-4-vadimp@nvidia.com \
--to=vadimp@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=peda@axentia.se \
--cc=wsa@the-dreams.de \
/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).