From: David Brownell <david-b@pacbell.net>
To: Tony Lindgren <tony@atomide.com>
Cc: Linux OMAP <linux-omap-open-source@linux.omap.com>
Subject: Re: Common code for TSC 2101 and 2102
Date: Fri, 10 Aug 2007 20:04:59 -0700 [thread overview]
Message-ID: <200708102004.59747.david-b@pacbell.net> (raw)
In-Reply-To: <20070810072912.GE8658@atomide.com>
On Friday 10 August 2007, Tony Lindgren wrote:
> I'll be pushing Andrzej's patch today.
I saw it ... it was after I've finally started to dig
out from under my pile of patches going upstream, and
even fired up an OMAP build again! :)
Glad to see this. Now I'll have to actually take
more of a real look at it. Presumably I'll have a
few updates, and then will feel it's time to start
pushing three patches upstream from this big one:
- drivers/spi/tsc210x.c core, which I can handle;
- drivers/hwmon/tsc210x_sensors.c, through hwmon;
- drivers/input/touchscreen/tsc210x_ts.c, through input;
- ... and later sound/soc/.../something.c, TBD.
I figure an initial upstream merge should included
one or both of { touchscreen, hwmon } in addition
to the core. Hitting 2.6.24-early should be possible.
- Dave
next prev parent reply other threads:[~2007-08-11 3:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 13:44 Common code for TSC 2101 and 2102 andrzej zaborowski
2007-07-13 6:46 ` Trilok Soni
2007-07-13 7:10 ` Trilok Soni
2007-07-13 19:29 ` andrzej zaborowski
2007-07-13 20:04 ` David Brownell
2007-08-10 7:29 ` Tony Lindgren
2007-08-11 3:04 ` David Brownell [this message]
2007-08-13 7:05 ` Tony Lindgren
2007-08-14 5:34 ` David Brownell
2007-09-23 22:37 ` andrzej zaborowski
2007-08-14 5:38 ` [patch 2.6.23-rc2-omap1] tsc210x cleanup David Brownell
2007-08-15 10:54 ` Tony Lindgren
2007-08-14 5:40 ` [patch 2.6.23-rc2-omap1] H4 support for tsc210x David Brownell
2007-08-14 6:45 ` David Brownell
2007-08-15 10:54 ` Tony Lindgren
2007-07-13 18:38 ` Common code for TSC 2101 and 2102 David Brownell
2007-07-15 20:18 ` David Brownell
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=200708102004.59747.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.com \
--cc=tony@atomide.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