linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org, Jiri Kosina <jikos@kernel.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] hid: i2c-hid: move header file out of I2C realm
Date: Mon, 22 May 2017 09:56:00 +0200	[thread overview]
Message-ID: <20170522075600.GA11492@mail.corp.redhat.com> (raw)
In-Reply-To: <20170521203033.6146-2-wsa@the-dreams.de>

On May 21 2017 or thereabouts, Wolfram Sang wrote:
> include/linux/i2c is not for client devices. Move the header file to a
> more appropriate location.
> 
> Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
> ---

Acked-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>

Cheers,
Benjamin

>  drivers/hid/i2c-hid/i2c-hid.c                  | 2 +-
>  include/linux/{i2c => platform_data}/i2c-hid.h | 0
>  2 files changed, 1 insertion(+), 1 deletion(-)
>  rename include/linux/{i2c => platform_data}/i2c-hid.h (100%)
> 
> diff --git a/drivers/hid/i2c-hid/i2c-hid.c b/drivers/hid/i2c-hid/i2c-hid.c
> index 8daa8ce64ebba5..841aa43526eba4 100644
> --- a/drivers/hid/i2c-hid/i2c-hid.c
> +++ b/drivers/hid/i2c-hid/i2c-hid.c
> @@ -40,7 +40,7 @@
>  #include <linux/of.h>
>  #include <linux/regulator/consumer.h>
>  
> -#include <linux/i2c/i2c-hid.h>
> +#include <linux/platform_data/i2c-hid.h>
>  
>  #include "../hid-ids.h"
>  
> diff --git a/include/linux/i2c/i2c-hid.h b/include/linux/platform_data/i2c-hid.h
> similarity index 100%
> rename from include/linux/i2c/i2c-hid.h
> rename to include/linux/platform_data/i2c-hid.h
> -- 
> 2.11.0
> 

  reply	other threads:[~2017-05-22  7:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-21 20:30 [PATCH 0/1] hid: move include files out of include/linux/i2c Wolfram Sang
2017-05-21 20:30 ` [PATCH 1/1] hid: i2c-hid: move header file out of I2C realm Wolfram Sang
2017-05-22  7:56   ` Benjamin Tissoires [this message]
2017-05-22 12:01   ` Jiri Kosina

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=20170522075600.GA11492@mail.corp.redhat.com \
    --to=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).