From: Wolfram Sang <wsa@the-dreams.de>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Cc: linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@savoirfairelinux.com
Subject: Re: [PATCH] misc: (at24) move header to linux/platform_data/
Date: Fri, 23 Aug 2013 21:02:47 +0200 [thread overview]
Message-ID: <20130823190247.GA3821@katana> (raw)
In-Reply-To: <1377283100-10390-1-git-send-email-vivien.didelot@savoirfairelinux.com>
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
On Fri, Aug 23, 2013 at 02:38:20PM -0400, Vivien Didelot wrote:
> This patch moves the at24.h header from include/linux/i2c to
> include/linux/platform_data and updates existing support accordingly.
This message explains what the patch does but not why the change is
wanted. I'd be surprised if we really want *all* platform_data in one
single directory? Is this patch part of a bigger series? That being said
i2c is not the best place for this include, in deed...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] misc: (at24) move header to linux/platform_data/
Date: Fri, 23 Aug 2013 21:02:47 +0200 [thread overview]
Message-ID: <20130823190247.GA3821@katana> (raw)
In-Reply-To: <1377283100-10390-1-git-send-email-vivien.didelot@savoirfairelinux.com>
On Fri, Aug 23, 2013 at 02:38:20PM -0400, Vivien Didelot wrote:
> This patch moves the at24.h header from include/linux/i2c to
> include/linux/platform_data and updates existing support accordingly.
This message explains what the patch does but not why the change is
wanted. I'd be surprised if we really want *all* platform_data in one
single directory? Is this patch part of a bigger series? That being said
i2c is not the best place for this include, in deed...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130823/b3400d2a/attachment.sig>
next prev parent reply other threads:[~2013-08-23 19:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 18:38 [PATCH] misc: (at24) move header to linux/platform_data/ Vivien Didelot
2013-08-23 18:38 ` Vivien Didelot
2013-08-23 18:38 ` Vivien Didelot
2013-08-23 19:02 ` Wolfram Sang [this message]
2013-08-23 19:02 ` Wolfram Sang
2013-08-23 19:19 ` Vivien Didelot
2013-08-23 19:19 ` Vivien Didelot
2013-08-23 19:19 ` Vivien Didelot
2013-08-23 19:26 ` Alexander Shiyan
2013-08-23 19:26 ` Alexander Shiyan
2013-08-23 19:26 ` Alexander Shiyan
2013-08-23 19:40 ` Vivien Didelot
2013-08-23 19:40 ` Vivien Didelot
2013-08-23 20:11 ` Wolfram Sang
2013-08-23 20:11 ` Wolfram Sang
2013-08-23 20:11 ` Wolfram Sang
2013-08-23 20:45 ` Vivien Didelot
2013-08-23 20:45 ` Vivien Didelot
2013-08-23 20:45 ` Vivien Didelot
2013-09-26 20:09 ` Vivien Didelot
2013-09-26 20:09 ` Vivien Didelot
2013-09-26 20:09 ` Vivien Didelot
2013-09-27 16:32 ` Wolfram Sang
2013-09-27 16:32 ` Wolfram Sang
2013-09-27 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=20130823190247.GA3821@katana \
--to=wsa@the-dreams.de \
--cc=kernel@savoirfairelinux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.