linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linus.ml.walleij@gmail.com (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM mandatory barriers
Date: Tue, 2 Mar 2010 10:50:10 +0100	[thread overview]
Message-ID: <63386a3d1003020150o6a7bf041mf9c32fb989430063@mail.gmail.com> (raw)
In-Reply-To: <20100223105806.11048.16585.stgit@e102109-lin.cambridge.arm.com>

2010/2/23 Catalin Marinas <catalin.marinas@arm.com>:

> This is a follow up to a previous patch I posted on the implementation
> of the mandatory barriers on ARM. The third patch adds support for the
> L2x0 cache sync operation and the last patch implements the
> RealView-specific mandatory barriers.

Catalin what is the status of these patches? I don't find them in the
patch tracker, are they being reworked? (Sorry if I missed some of the
discussion here...)

Linus Walleij

  reply	other threads:[~2010-03-02  9:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-23 11:00 [PATCH 0/4] ARM mandatory barriers Catalin Marinas
2010-03-02  9:50 ` Linus Walleij [this message]
2010-03-02  9:58   ` Catalin Marinas

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=63386a3d1003020150o6a7bf041mf9c32fb989430063@mail.gmail.com \
    --to=linus.ml.walleij@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).