All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: akpm@osdl.org
Cc: adaplas@pol.net, linux-fbdev-devel@lists.sourceforge.net,
	vojtech@suse.cz, linux-kernel@vger.kernel.org
Subject: [patch 0/8] Corgi (Sharp Zaurus SL-c7x0) Driver Updates
Date: Fri, 29 Jul 2005 10:46:23 +0100	[thread overview]
Message-ID: <1122630383.7747.85.camel@localhost.localdomain> (raw)

This is a series of driver updates for the Sharp Zaurus SL-C7x0. All the
patches have been seen by the subsystem maintainers at some point. Some
of the input patches seem to be lost in the system (since March) and
given the mainline corgi keyboard code doesn't even compile at the
moment, I'd like to see some of these making mainline sooner rather than
later. The w100fb patch depends on the corgi touchscreen cleanup patch
which is why this hasn't been merged as yet. This patch series seems the
simplest way to resolve things.

Patches 1-7 only affect the Zaurus platform and are being used by Zaurus
users in preference to mainline kernels so merging makes a lot of sense
and should be minimal risk for anyone else. They're also all patches
against code I effectively maintain.

Patch 8 is the final key to resolving an input key vs. switch issue and
I'm happy to wait for the input maintainer to merge that if appropriate.
I've included it for completeness as previous versions that are around
are suffering bitrot.

Hopefully these are all good candidates for -mm and then mainline.

Richard
(Corgi Maintainer)




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <rpurdie@rpsys.net>
To: akpm@osdl.org
Cc: adaplas@pol.net, linux-fbdev-devel@lists.sourceforge.net,
	vojtech@suse.cz, linux-kernel@vger.kernel.org
Subject: [patch 0/8] Corgi (Sharp Zaurus SL-c7x0) Driver Updates
Date: Fri, 29 Jul 2005 10:46:23 +0100	[thread overview]
Message-ID: <1122630383.7747.85.camel@localhost.localdomain> (raw)

This is a series of driver updates for the Sharp Zaurus SL-C7x0. All the
patches have been seen by the subsystem maintainers at some point. Some
of the input patches seem to be lost in the system (since March) and
given the mainline corgi keyboard code doesn't even compile at the
moment, I'd like to see some of these making mainline sooner rather than
later. The w100fb patch depends on the corgi touchscreen cleanup patch
which is why this hasn't been merged as yet. This patch series seems the
simplest way to resolve things.

Patches 1-7 only affect the Zaurus platform and are being used by Zaurus
users in preference to mainline kernels so merging makes a lot of sense
and should be minimal risk for anyone else. They're also all patches
against code I effectively maintain.

Patch 8 is the final key to resolving an input key vs. switch issue and
I'm happy to wait for the input maintainer to merge that if appropriate.
I've included it for completeness as previous versions that are around
are suffering bitrot.

Hopefully these are all good candidates for -mm and then mainline.

Richard
(Corgi Maintainer)



             reply	other threads:[~2005-07-29  9:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29  9:46 Richard Purdie [this message]
2005-07-29  9:46 ` [patch 0/8] Corgi (Sharp Zaurus SL-c7x0) Driver Updates Richard Purdie

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=1122630383.7747.85.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=adaplas@pol.net \
    --cc=akpm@osdl.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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.