From: Cory Maccarrone <darkstar6262@gmail.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
Michael Hennerich <michael.hennerich@analog.com>,
Robin Getz <rgetz@blackfin.uclinux.org>
Subject: Re: [git pull] Input updates for 2.6.34-rc0
Date: Tue, 9 Mar 2010 08:15:06 -0800 [thread overview]
Message-ID: <6cb013311003090815o7ec1de7fna68150e469855ce5@mail.gmail.com> (raw)
In-Reply-To: <8bd0f97a1003090644p19fb7dacqe1f2fb3adee3fa7a@mail.gmail.com>
On Tue, Mar 9, 2010 at 6:44 AM, Mike Frysinger <vapier.adi@gmail.com> wrote:
> On Mon, Mar 1, 2010 at 03:03, Dmitry Torokhov wrote:
>> Hi Linus,
>>
>> Please pull from:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
>> or
>> master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
>>
>> to receive first round of updates for the input subsystem.
>
> i'm trying to figure out what the problem is with the ADXL34x and
> AD714x drivers you seem to have accepted (at least, you didnt say
> there was anything left for us to do). i would have expected them to
> be in 2.6.33/2.6.34 already, but it seems they arent moving now. so
> what's up ?
> -mike
> --
> To unsubscribe from this list: send the line "unsubscribe linux-input" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
I'm in the same boat with my TSC2046 driver. Any idea why this hasn't
moved? I have received no comments, nor has the driver been included
/ accepted. Do I need to make revisions, or can it be included?
- Cory
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-09 16:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 8:03 [git pull] Input updates for 2.6.34-rc0 Dmitry Torokhov
2010-03-09 14:44 ` Mike Frysinger
2010-03-09 16:15 ` Cory Maccarrone [this message]
2010-03-09 17:53 ` Dmitry Torokhov
2010-03-09 17:51 ` Dmitry Torokhov
2010-03-09 17:58 ` Mike Frysinger
2010-03-09 18:10 ` Dmitry Torokhov
2010-03-09 18:13 ` Mike Frysinger
2010-03-09 18:20 ` Dmitry Torokhov
2010-03-09 19:39 ` Robin Getz
2010-03-10 8:30 ` Hennerich, Michael
2010-03-12 20:55 ` Robin Getz
2010-03-13 8:44 ` Dmitry Torokhov
2010-03-22 6:37 ` Dmitry Torokhov
2010-03-22 7:44 ` Mike Frysinger
2010-03-09 18:18 ` Jonathan Cameron
2010-03-09 18:21 ` Mike Frysinger
2010-03-09 19:08 ` Jonathan Cameron
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=6cb013311003090815o7ec1de7fna68150e469855ce5@mail.gmail.com \
--to=darkstar6262@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=rgetz@blackfin.uclinux.org \
--cc=vapier.adi@gmail.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).