From: Tony Lindgren <tony@atomide.com>
To: Imre Deak <imre.deak@nokia.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: is dynamic tick working?
Date: Mon, 15 May 2006 02:22:54 -0700 [thread overview]
Message-ID: <20060515092253.GD8368@atomide.com> (raw)
In-Reply-To: <446793B2.6040408@nokia.com>
* Imre Deak <imre.deak@nokia.com> [060514 13:31]:
> ext David Brownell wrote:
> >On Sunday 14 May 2006 10:57 am, Imre Deak wrote:
> >> The patch is already in the mainline
> >>tree, I've also sent it to Tony after I noticed it's missing from the
> >>OMAP tree. My fault, I should've kept the driver up-to-date in both
> >>trees..
> >
> >Understandable, given how long it took to get those patches merged
> >upstream! Plus the fact that the version in the OMAP tree was working
> >around byteswap bugs on the Microwire SPI driver ... I'm not sure I'd
> >have expected Tony to resolve all the merge conflicts right unless he
> >were more involved in sorting out those issues.
>
> Yep, to make it work I fixed the thing in the wrong place.
>
> >
> >So let's see. Other than those recent patches resolving those byteswap
> >bugs, and the hwmon features (not all merged upstream yet, sigh), are
> >there any reasons left for the OMAP version of that driver to differ from
> >the upstream one?
>
> No, they must be in sync now. Since the changes went to mainline and to
> the OMAP tree through different changesets (b/c the above wrong fix et
> al) and now the OMAP version is out of sync, I've sent a patchset to
> Tony to bring it up-to-date.
>
> >
> >My understanding is that thanks (!) mostly to your updates, we're almost
> >ready to say OMAP can use the same version of ads7846 that's upstream,
> >and that the omap_uwire driver could also go upstream. And given an OSK
> >version of that new routine, that Mistral support could also go upstream.
> >Does that sound right?
>
> Yes, the ads7846 and omap_uwire should be ok - and identical with
> upstream after the above patches.
OK, I've pushed Imre's patches. Can you check that everything got
patched OK?
Regards,
Tony
next prev parent reply other threads:[~2006-05-15 9:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 2:05 is dynamic tick working? David Brownell
2006-05-14 10:49 ` Tony Lindgren
2006-05-14 16:19 ` David Brownell
2006-05-14 17:57 ` Imre Deak
2006-05-14 19:20 ` David Brownell
2006-05-14 20:31 ` Imre Deak
2006-05-15 9:22 ` Tony Lindgren [this message]
2006-05-15 22:11 ` David Brownell
2006-05-16 6:59 ` Tony Lindgren
2006-05-26 23:44 ` Tony Lindgren
2006-05-15 9:26 ` Tony Lindgren
2006-05-15 17:33 ` Linux On TI Omap850 Vince
2006-05-16 6:52 ` Tony Lindgren
2006-05-16 14:11 ` Brian Swetland
2006-05-16 13:32 ` is dynamic tick working? Imre Deak
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=20060515092253.GD8368@atomide.com \
--to=tony@atomide.com \
--cc=imre.deak@nokia.com \
--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