From: Wolfram Sang <wsa@the-dreams.de>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-i2c@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
rtc-linux@googlegroups.com
Subject: Re: [PATCH 1/3] mfd: dm355evm_msp: move header file out of I2C realm
Date: Mon, 14 Aug 2017 10:25:40 +0200 [thread overview]
Message-ID: <20170814082540.g3w3aur2nwuf5s6h@ninjato> (raw)
In-Reply-To: <20170814064336.secnn77amfjgbltw@dell>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
On Mon, Aug 14, 2017 at 07:43:36AM +0100, Lee Jones wrote:
> On Sun, 13 Aug 2017, Wolfram Sang wrote:
>
> > On Tue, May 23, 2017 at 08:17:27AM +0100, Lee Jones wrote:
> > > On Mon, 22 May 2017, 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>
> > > > ---
> > > > drivers/input/misc/dm355evm_keys.c | 2 +-
> > >
> > > > drivers/mfd/dm355evm_msp.c | 2 +-
> > >
> > > For my own reference:
> > > Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
> >
> > Does that mean it will be in 4.14? Or is something else needed?
>
> Can this patch be applied on its own, or does it have dependencies?
These patches are self-contained; they only move an include file from A
to B.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-08-14 8:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 22:02 [PATCH 0/3] mfd: move include files out of include/linux/i2c Wolfram Sang
2017-05-21 22:02 ` [PATCH 1/3] mfd: dm355evm_msp: move header file out of I2C realm Wolfram Sang
2017-05-22 9:14 ` Alexandre Belloni
2017-05-22 23:36 ` Dmitry Torokhov
2017-05-23 7:17 ` Lee Jones
2017-08-13 13:34 ` Wolfram Sang
2017-08-14 6:43 ` Lee Jones
2017-08-14 8:25 ` Wolfram Sang [this message]
2017-05-21 22:02 ` [PATCH 2/3] mfd: tps65010: " Wolfram Sang
2017-05-22 7:24 ` Greg Kroah-Hartman
2017-05-22 7:34 ` Krzysztof Kozlowski
2017-05-23 7:18 ` Lee Jones
2017-08-13 13:34 ` Wolfram Sang
2017-08-14 6:43 ` Lee Jones
2017-08-14 8:44 ` Lee Jones
2017-08-14 16:21 ` Tony Lindgren
2017-08-14 16:29 ` Wolfram Sang
2017-05-29 9:19 ` Bartlomiej Zolnierkiewicz
2017-05-21 22:02 ` [PATCH 3/3] mfd: twl: " Wolfram Sang
2017-05-22 7:25 ` Greg Kroah-Hartman
2017-05-22 9:14 ` Alexandre Belloni
2017-05-22 9:52 ` Mark Brown
2017-05-22 10:28 ` Wolfram Sang
2017-05-22 11:12 ` Mark Brown
2017-05-22 10:27 ` Sebastian Reichel
2017-05-22 20:34 ` Jonathan Cameron
2017-05-22 23:37 ` Dmitry Torokhov
2017-05-23 7:16 ` Lee Jones
2017-05-23 7:21 ` Wolfram Sang
2017-05-23 7:42 ` Kishon Vijay Abraham I
2017-05-29 9:20 ` Bartlomiej Zolnierkiewicz
2017-07-06 6:44 ` Thierry Reding
2017-07-06 7:03 ` Lee Jones
2017-08-13 13:37 ` Wolfram Sang
2017-08-14 6:42 ` Lee Jones
2017-08-14 8:43 ` Wolfram Sang
2017-08-14 16:22 ` Tony Lindgren
2017-08-14 16:27 ` Daniel Thompson
2017-08-14 16:32 ` 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=20170814082540.g3w3aur2nwuf5s6h@ninjato \
--to=wsa@the-dreams.de \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=dmitry.torokhov@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
/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).