Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Gabor Juhos <juhosg@openwrt.org>
Cc: linux-mips@linux-mips.org, stable@vger.kernel.org
Subject: Re: [PATCH] MIPS: ath79: fix CPU/DDR frequency calculation for SRIF PLLs
Date: Sun, 23 Sep 2012 19:48:51 +0200	[thread overview]
Message-ID: <20120923174851.GG13842@linux-mips.org> (raw)
In-Reply-To: <1347105741-23091-1-git-send-email-juhosg@openwrt.org>

On Sat, Sep 08, 2012 at 02:02:21PM +0200, Gabor Juhos wrote:

Applied but I had to fix a conflict:

@@ -65,6 +65,8 @@
 #define AR934X_WMAC_SIZE	0x20000
 #define AR934X_EHCI_BASE	0x1b000000
 #define AR934X_EHCI_SIZE	0x200
+#define AR934X_SRIF_BASE	(AR71XX_APB_BASE + 0x00116000)
+#define AR934X_SRIF_SIZE	0x1000
 
 /*
  * DDR_CTRL block

The EHCI lines don't exist yet.  Seems harmless though.

  Ralf

  parent reply	other threads:[~2012-09-23 17:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-08 12:02 [PATCH] MIPS: ath79: fix CPU/DDR frequency calculation for SRIF PLLs Gabor Juhos
2012-09-08 12:02 ` Gabor Juhos
2012-09-23 17:48 ` Ralf Baechle [this message]
2012-09-24  7:26   ` Gabor Juhos

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=20120923174851.GG13842@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=juhosg@openwrt.org \
    --cc=linux-mips@linux-mips.org \
    --cc=stable@vger.kernel.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