linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
	mans@mansr.com, khilman@deeprootsystems.com,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/5] omap4: l2x0 fixes and cleanup
Date: Sat, 18 Dec 2010 09:39:53 -0800	[thread overview]
Message-ID: <20101218173952.GU5941@atomide.com> (raw)
In-Reply-To: <8e452d427e061b34d119e860a0e30b31@mail.gmail.com>

* Santosh Shilimkar <santosh.shilimkar@ti.com> [101213 21:08]:
> ping
...

> > How about merging this series in omap-testing if you are ok
> > with it. Patch  " ARM: l2x0: Add aux control register bitfields"
> > is already acked by Catalin.

Sorry for the delay on this series, applying.

Regards,

Tony

      reply	other threads:[~2010-12-18 17:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19 17:31 [PATCH 0/5] omap4: l2x0 fixes and cleanup Santosh Shilimkar
2010-11-19 17:31 ` [PATCH 1/5] ARM: l2x0: Add aux control register bitfields Santosh Shilimkar
2010-11-19 17:31   ` [PATCH 2/5] omap4: l2x0: Construct the AUXCTRL value using defines Santosh Shilimkar
2010-11-19 17:31     ` [PATCH 3/5] omap4: l2x0: enable instruction and data prefetching Santosh Shilimkar
2010-11-19 17:31       ` [PATCH 4/5] omap4: l2x0: Set share override bit Santosh Shilimkar
2010-11-19 17:31         ` [PATCH 5/5] omap4: l2x0: Enable early BRESP bit Santosh Shilimkar
2010-11-19 18:32           ` Måns Rullgård
2010-11-20 10:08             ` Santosh Shilimkar
2010-11-22 20:11     ` [PATCH 2/5] omap4: l2x0: Construct the AUXCTRL value using defines Kevin Hilman
2010-11-22 20:21       ` Måns Rullgård
2010-11-19 18:13   ` [PATCH 1/5] ARM: l2x0: Add aux control register bitfields Catalin Marinas
2010-12-02 11:57 ` [PATCH 0/5] omap4: l2x0 fixes and cleanup Santosh Shilimkar
2010-12-14  5:08   ` Santosh Shilimkar
2010-12-18 17:39     ` 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=20101218173952.GU5941@atomide.com \
    --to=tony@atomide.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mans@mansr.com \
    --cc=nm@ti.com \
    --cc=santosh.shilimkar@ti.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;
as well as URLs for NNTP newsgroup(s).