public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] Fix ADS7846 dependencies
Date: Fri, 22 Dec 2006 12:01:12 -0800	[thread overview]
Message-ID: <20061222200111.GF2449@atomide.com> (raw)
In-Reply-To: <200612212255.56224.david-b@pacbell.net>

* David Brownell <david-b@pacbell.net> [061221 22:56]:
> On Thursday 21 December 2006 3:31 pm, Tony Lindgren wrote:
> > * Tony Lindgren <tony@atomide.com> [061110 16:44]:
> > > 
> > > This looks OK to me, Dave any comments?
> 
> Actually I'm trying to sync up the mainline code with what's
> in the OMA tree; they've diverged a bit too much for it to
> be straightforward.
> 
> The hwmon related parts of that sync-up, against mainline, are at:
> 
> http://lists.lm-sensors.org/pipermail/lm-sensors/2006-December/018484.html
> 
> and the behavioral summary is that the hwmon functionality won't
> exist without someone separately configuring hwmon.  :)
> 
> 
> What this is going to mean is that at some point all the updates
> specific to the OMAP tree should just be wiped out by pulling down
> the version from the main tree.  After that, I hope there won't be
> divergence again ...
> 
> (The original reason for divergence was that the OMAP version had
> workarounds for byteswap bugs in the omap_uwire driver.  Now that
> those are gone, there's no longer a reason to diverge...)

Great, we'll switch to the mainline version when your patches are
integrated.

Tony

      reply	other threads:[~2006-12-22 20:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10 13:27 [PATCH] Fix ADS7846 dependencies Arnaud Patard
2006-11-11  0:37 ` Tony Lindgren
2006-12-21 23:31   ` Tony Lindgren
2006-12-22  6:55     ` David Brownell
2006-12-22 20:01       ` 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=20061222200111.GF2449@atomide.com \
    --to=tony@atomide.com \
    --cc=david-b@pacbell.net \
    --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