public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Pavel Machek <pavel@ucw.cz>, Arjan Van de Ven <arjanv@redhat.com>,
	Christoph Hellwig <hch@infradead.org>
Cc: Mark Underwood <basicmark@yahoo.com>,
	rpurdie@rpsys.net, lenz@cs.wisc.edu,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [patch] ucb1x00: touchscreen cleanups
Date: Sat, 30 Jul 2005 22:03:40 +0100	[thread overview]
Message-ID: <20050730220340.K26592@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050730204658.GC9418@elf.ucw.cz>; from pavel@ucw.cz on Sat, Jul 30, 2005 at 10:46:58PM +0200

On Sat, Jul 30, 2005 at 10:46:58PM +0200, Pavel Machek wrote:
> Hi!
> 
> > > > Note that I'm maintaining the code and will be
> > > > publishing a new set
> > > > of patches for it based upon Pavel's fixes.
> > > 
> > > Thanks. I'll check them out then.
> > 
> > Since there appears to be some interest in these, I'll set about
> > converting the audio bits to ALSA rather than Nico's SA11x0 audio
> > driver.  I thought no one was using these chips anymore, and the
> > driver was dead!
> > 
> > I've recently edited the mcp structure which may make things less
> > awkward for others, and I'll continue moving in that direction
> > with this driver.
> > 
> > You can get the updated patches at:
> > 
> > 	http://zeniv.linux.org.uk/pub/people/rmk/ucb/
> 
> Okay, what's the plan with mainstreaming those? Do they stay in
> drivers/misc?

Let me put the second question a slightly different way: can anyone
think of a better way to organise the files which makes more sense
and doesn't end up with just a couple of files for the core UCB
and MCP support in some random directory elsewhere?

Arjan?  hch?  any comments / good ideas?

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2005-07-30 21:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26  7:46 [patch] ucb1x00: touchscreen cleanups Pavel Machek
2005-07-26  8:04 ` Mark Underwood
2005-07-26  8:07   ` Pavel Machek
2005-07-30  9:22   ` Russell King
2005-07-30 11:33     ` Mark Underwood
2005-07-30 20:28       ` Russell King
2005-07-30 20:46         ` Pavel Machek
2005-07-30 21:03           ` Russell King [this message]
2005-07-31 22:11             ` Mark Underwood
2005-07-31 22:33               ` Richard Purdie
2005-07-31 22:49                 ` Pavel Machek
2005-08-01  8:02                 ` How do we handle multi-function devices? [was Re: [patch] ucb1x00: touchscreen cleanups] Mark Underwood
2005-07-30  9:17 ` [patch] ucb1x00: touchscreen cleanups Russell King
2005-07-30  9:23   ` Pavel Machek

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=20050730220340.K26592@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=arjanv@redhat.com \
    --cc=basicmark@yahoo.com \
    --cc=hch@infradead.org \
    --cc=lenz@cs.wisc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rpurdie@rpsys.net \
    /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