From: Tony Lindgren <tony@atomide.com>
To: Arnaud Patard <arnaud.patard@rtp-net.org>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Broken ads7846 touchscreen, was: [PATCH] ARM: OMAP: Fix SPI merge issues and reintroduce omap_uwire.c
Date: Mon, 5 Mar 2007 01:59:46 -0800 [thread overview]
Message-ID: <20070305095626.GB17801@atomide.com> (raw)
In-Reply-To: <85vehgdba0.fsf@orfeo.duckcorp.org>
Hi,
* Arnaud Patard <arnaud.patard@rtp-net.org> [070304 12:07]:
> Dirk Behme <dirk.behme@googlemail.com> writes:
>
> > Arnaud Patard (Rtp) wrote:
> >> Dirk Behme <dirk.behme@googlemail.com> writes:
> >>
> >>
> >>>Is there any special reason why
> >>>
> >>>http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=commit;h=ba6d3cf6f7900c7586cca6bbd9dca55d7c6386fb
> >>>
> >>>deleted drivers/spi/omap_uwire.c?
> >>
> >>
> >> looks like forgotten git-update-index or something like that. I didn't
> >> check closely but I bet that this conflicts explains also why the
> >> ads7846 touchscreen driver doesn't work. I had to take the versions from
> >> the old linux-omap-2.6 tree to get my touchscreen back :(
Sorry, I must have hosed it while merging. I'll make sure drivers/spi
is in sync with mainline today. If we still have some necessary fixes for
spi, they should be sent to LKML for integration.
> > Do you can make a diff between the old and new version and send a
> > patch?
>
> Sure. I'll send it in a new mail and it will probably need review from the
> ads784x guys.
We should make use the ads784x code is also in sync with mainline.
Regards,
Tony
prev parent reply other threads:[~2007-03-05 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 12:13 [PATCH] ARM: OMAP: Fix SPI merge issues and reintroduce omap_uwire.c Dirk Behme
2007-03-04 12:28 ` Arnaud Patard
2007-03-04 16:38 ` Broken ads7846 touchscreen, was: " Dirk Behme
2007-03-04 20:05 ` Arnaud Patard
2007-03-05 9:59 ` Tony Lindgren [this message]
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=20070305095626.GB17801@atomide.com \
--to=tony@atomide.com \
--cc=arnaud.patard@rtp-net.org \
--cc=linux-omap-open-source@linux.omap.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