All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>, 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: Thu, 16 Sep 2010 13:49:35 -0700	[thread overview]
Message-ID: <20100916204935.GP29610@atomide.com> (raw)
In-Reply-To: <AANLkTinXdow4tzmwpx6nRe5VCN5Q8_aKz9EibxKinWWO@mail.gmail.com>

* Gadiyar, Anand <gadiyar@ti.com> [100916 13:16]:
> On Fri, Sep 17, 2010 at 12:27 AM, Tony Lindgren <tony@atomide.com> wrote:
> 
> For the past - OMAP3 and before - we'll do our best to scrub all internal
> trees for missing bugs/features/what not and hopefully this will
> go upstream as we discover those.
> 
> Sounds fair?

Sounds fair. But it might be worth checking that you guys have a system
in place for collecting omap specific fixes and promptly merging them
upstream to the mainline tree.

Regards,

Tony

  reply	other threads:[~2010-09-16 20:49 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
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 [this message]
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=20100916204935.GP29610@atomide.com \
    --to=tony@atomide.com \
    --cc=gadiyar@ti.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.