linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Dietmar Eggemann <dietmar.eggemann-5wv7dgnIgG8@public.gmane.org>
Subject: Re: [PATCH 2/2] ARM: tegra: use CS_LAR_KEY definition instead of 0xC5ACCE55
Date: Tue, 26 Mar 2013 14:34:53 -0600	[thread overview]
Message-ID: <5152066D.8080804@wwwdotorg.org> (raw)
In-Reply-To: <1364235552-17851-2-git-send-email-will.deacon-5wv7dgnIgG8@public.gmane.org>

On 03/25/2013 12:19 PM, Will Deacon wrote:
> When enabling coresight on secondary cores for tegra, make use of our
> fancy new definition for the magic lock code.

The code you're editing has actually been removed in the 3.10 cycle, so
there's no need for this patch any more.

  parent reply	other threads:[~2013-03-26 20:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 18:19 [PATCH 1/2] ARM: tegra: use setup_mm_for_reboot rather than explicit pgd switch Will Deacon
     [not found] ` <1364235552-17851-1-git-send-email-will.deacon-5wv7dgnIgG8@public.gmane.org>
2013-03-25 18:19   ` [PATCH 2/2] ARM: tegra: use CS_LAR_KEY definition instead of 0xC5ACCE55 Will Deacon
     [not found]     ` <1364235552-17851-2-git-send-email-will.deacon-5wv7dgnIgG8@public.gmane.org>
2013-03-26 20:34       ` Stephen Warren [this message]
2013-03-26 20:38   ` [PATCH 1/2] ARM: tegra: use setup_mm_for_reboot rather than explicit pgd switch Stephen Warren

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=5152066D.8080804@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=dietmar.eggemann-5wv7dgnIgG8@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=will.deacon-5wv7dgnIgG8@public.gmane.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).