All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Jon Hunter <jon-hunter@ti.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	khilman@deeprootsystems.com
Subject: Re: [PATCH] omap3: Prevent SDRC deadlock when L3 is changing frequency
Date: Wed, 15 Sep 2010 15:40:07 -0700	[thread overview]
Message-ID: <20100915224007.GJ4174@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1009151300190.458@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [100915 12:07]:
> > 
> > This change has been commited to both TI's android 2.6.29 and 2.6.32 kernels.
> > The commits can be viewed here:
> > http://git.omapzoom.org/?p=kernel/omap.git;a=commit;h=5679c7b1142f3cc2b9285181d53f6b40c4d0296d
> > http://git.omapzoom.org/?p=kernel/omap.git;a=commit;h=cf16e57823575d98e9d5165aa7a498ffb751c940
> > 
> > This patch has been rebased on the latest linux-omap tree and tested on
> > Kevin Hilman's pm branch.

Sounds like a very important fix. But also a good example of how
messed up things are with the TI Linux kernel development.

Why has this fix it been sitting in some TI internal tree since
Fri, 12 Mar 2010?

This same bug has been patched in three different trees? But not in
the mainline kernel?

And this is happening all the time with the TI fixes.

Tony

  reply	other threads:[~2010-09-15 22:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21 16:02 [PATCH] omap3: Prevent SDRC deadlock when L3 is changing frequency Jon Hunter
2010-09-15 19:15 ` Paul Walmsley
2010-09-15 22:40   ` Tony Lindgren [this message]
2010-09-15 23:10     ` Paul Walmsley
2010-09-16  4:58       ` Gadiyar, Anand
2010-09-16 18:57         ` Tony Lindgren
2010-09-16 20:23           ` Gadiyar, Anand
2010-09-16 20:49             ` Tony Lindgren
2010-09-17  0:05               ` Woodruff, Richard
2010-09-16  6:05   ` Woodruff, Richard
2010-09-16  6:24     ` Shilimkar, Santosh
2010-09-17 18:30       ` Paul Walmsley
2010-09-15 21:38 ` Paul Walmsley

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=20100915224007.GJ4174@atomide.com \
    --to=tony@atomide.com \
    --cc=jon-hunter@ti.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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 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.