From: Linus Walleij <linus.walleij@linaro.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Alexandra Chin <alexandra.chin@tw.synaptics.com>,
Henrik Rydberg <rydberg@euromail.se>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Input <linux-input@vger.kernel.org>,
Linus Walleij <linus.walleij@stericsson.com>,
Naveen Kumar Gaddipati <naveen.gaddipati@stericsson.com>,
Mahesh Srinivasan <msrinivasan@synaptics.com>,
Alex Chang <alex.chang@tw.synaptics.com>,
Scott Lin <scott.lin@tw.synaptics.com>,
Christopher Heiny <Cheiny@synaptics.com>
Subject: Re: [RFC] staging: ste_rmi4: merge into the main kernel tree
Date: Thu, 15 Nov 2012 20:05:41 +0100 [thread overview]
Message-ID: <CACRpkdbB5ijaRLmiB2DbFGunJQUUAM2+nhwBOOqSkMWQZVNHTQ@mail.gmail.com> (raw)
In-Reply-To: <20121115185522.GA4077@core.coreip.homeip.net>
On Thu, Nov 15, 2012 at 7:55 PM, Dmitry Torokhov
<dmitry.torokhov@gmail.com> wrote:
> On Thu, Nov 15, 2012 at 06:41:26PM +0100, Linus Walleij wrote:
>>
>> The benefit is that the ugliness in
>> drivers/staging/ste_rmi4/board-mop500-u8500uib-rmi4.c
>> can be avoided, as today we're unable to pass the compulsory
>> platform data in any sane way. I'm being told that this weak symbol
>> override actually does not really work... especially if there are more
>> than 1 I2C device on the bus :-P
>
> I am confused as to why this would be a benefit of ste_rmi4 over full
> RMI4 implementation from Christopher's group?
So we don't need to keep our real platform data and board files
out-of-tree like we've done for the last 2 years or so.
But I only said it's a benefit, not that I think it's a good idea.
> I think what we really need is to accelerate work on the full driver so
> it is in mainline in 3.9ish.
Yep, agreed.
Yours,
Linus Walleij
next prev parent reply other threads:[~2012-11-15 19:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 17:36 [PATCH v3] staging: ste_rmi4: Convert to Type-B support Alexandra Chin
2012-11-04 21:53 ` Henrik Rydberg
2012-11-05 6:01 ` Alexandra Chin
2012-11-12 11:59 ` Alexandra Chin
2012-11-07 5:49 ` [PATCH v4] " Alexandra Chin
2012-11-07 19:57 ` Henrik Rydberg
2012-11-08 4:01 ` Alexandra Chin
2012-11-08 7:05 ` [PATCH v5] " Alexandra Chin
2012-11-09 19:26 ` Henrik Rydberg
2012-11-12 16:40 ` Alexandra Chin
2012-11-12 17:20 ` Henrik Rydberg
2012-11-13 2:04 ` Alexandra Chin
2012-11-13 12:12 ` [PATCH v6] " Alexandra Chin
2012-11-13 17:53 ` Henrik Rydberg
2012-11-14 17:33 ` Alexandra Chin
2012-11-14 17:40 ` [RFC] staging: ste_rmi4: merge into the main kernel tree Alexandra Chin
2012-11-14 18:04 ` Dmitry Torokhov
2012-11-15 2:56 ` Alexandra Chin
2012-11-15 6:43 ` Dmitry Torokhov
2012-11-15 17:41 ` Linus Walleij
2012-11-15 18:55 ` Dmitry Torokhov
2012-11-15 19:05 ` Linus Walleij [this message]
2012-11-16 9:02 ` Alexandra Chin
2012-11-16 19:24 ` Dmitry Torokhov
2012-11-16 8:31 ` [PATCH v6] staging: ste_rmi4: Convert to Type-B support Alexandra Chin
2012-11-16 19:54 ` Henrik Rydberg
2012-11-16 19:50 ` Greg Kroah-Hartman
2012-12-06 11:30 ` Alexandra Chin
2012-12-06 16:34 ` Greg Kroah-Hartman
2012-12-07 4:01 ` Alexandra Chin
2012-12-07 5:11 ` Greg Kroah-Hartman
2012-12-07 6:45 ` Alexandra Chin
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=CACRpkdbB5ijaRLmiB2DbFGunJQUUAM2+nhwBOOqSkMWQZVNHTQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=Cheiny@synaptics.com \
--cc=alex.chang@tw.synaptics.com \
--cc=alexandra.chin@tw.synaptics.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msrinivasan@synaptics.com \
--cc=naveen.gaddipati@stericsson.com \
--cc=rydberg@euromail.se \
--cc=scott.lin@tw.synaptics.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).