linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org, Steven Miao <realmz6@gmail.com>,
	Michael Hennerich <michael.hennerich@analog.com>,
	Lee Jones <lee.jones@linaro.org>,
	Daniel Thompson <daniel.thompson@linaro.org>,
	Jingoo Han <jingoohan1@gmail.com>,
	adi-buildroot-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 1/2] video: adp8860: move header file out of I2C realm
Date: Mon, 29 May 2017 11:22:52 +0200	[thread overview]
Message-ID: <3553710.Yr6b9bAIsl@amdc3058> (raw)
In-Reply-To: <20170521220953.2602-2-wsa@the-dreams.de>

On Monday, May 22, 2017 12:09:52 AM 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: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>

> ---
>  arch/blackfin/mach-bf537/boards/stamp.c        | 2 +-
>  drivers/video/backlight/adp8860_bl.c           | 2 +-
>  include/linux/{i2c => platform_data}/adp8860.h | 0
>  3 files changed, 2 insertions(+), 2 deletions(-)
>  rename include/linux/{i2c => platform_data}/adp8860.h (100%)

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics

  reply	other threads:[~2017-05-29  9:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-21 22:09 [PATCH 0/2] video: move include files out of include/linux/i2c Wolfram Sang
2017-05-21 22:09 ` [PATCH 1/2] video: adp8860: move header file out of I2C realm Wolfram Sang
2017-05-29  9:22   ` Bartlomiej Zolnierkiewicz [this message]
2017-06-07 10:57   ` Daniel Thompson
2017-06-07 12:10     ` Michael Hennerich
2017-06-09  7:43   ` Lee Jones
2017-06-09  7:49     ` Lee Jones
2017-05-21 22:09 ` [PATCH 2/2] video: adp8870: " Wolfram Sang
2017-05-29  9:23   ` Bartlomiej Zolnierkiewicz
2017-06-07 10:57   ` Daniel Thompson
2017-06-09  7:43   ` Lee Jones
2017-06-09  7:48     ` Lee Jones

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=3553710.Yr6b9bAIsl@amdc3058 \
    --to=b.zolnierkie@samsung.com \
    --cc=adi-buildroot-devel@lists.sourceforge.net \
    --cc=daniel.thompson@linaro.org \
    --cc=jingoohan1@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.hennerich@analog.com \
    --cc=realmz6@gmail.com \
    --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).