From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org,
galak@kernel.crashing.org
Subject: Re: [PATCH] [v3] powerpc/8xxx: remove 85xx/86xx restrictions from fsl_guts.h
Date: Mon, 19 Mar 2012 16:37:42 +0000 [thread overview]
Message-ID: <20120319163742.GE5132@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1332173199-25877-1-git-send-email-timur@freescale.com>
[-- Attachment #1.1: Type: text/plain, Size: 552 bytes --]
On Mon, Mar 19, 2012 at 11:06:39AM -0500, Timur Tabi wrote:
> Remove the check for CONFIG_PPC_85xx and CONFIG_PPC_86xx from fsl_guts.h.
> The check was originally intended to allow the same header file to
> be used on 85xx and 86xx systems, even though the Global Utilities
> register could be different. It turns out that they're not actually
> different, and so the check is not necessary. In addition, neither
> macro is defined for 64-bit e5500 kernels, so that causes a build
> break.
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH] [v3] powerpc/8xxx: remove 85xx/86xx restrictions from fsl_guts.h
Date: Mon, 19 Mar 2012 16:37:42 +0000 [thread overview]
Message-ID: <20120319163742.GE5132@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1332173199-25877-1-git-send-email-timur@freescale.com>
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
On Mon, Mar 19, 2012 at 11:06:39AM -0500, Timur Tabi wrote:
> Remove the check for CONFIG_PPC_85xx and CONFIG_PPC_86xx from fsl_guts.h.
> The check was originally intended to allow the same header file to
> be used on 85xx and 86xx systems, even though the Global Utilities
> register could be different. It turns out that they're not actually
> different, and so the check is not necessary. In addition, neither
> macro is defined for 64-bit e5500 kernels, so that causes a build
> break.
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-03-19 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 16:06 [PATCH] [v3] powerpc/8xxx: remove 85xx/86xx restrictions from fsl_guts.h Timur Tabi
2012-03-19 16:06 ` Timur Tabi
2012-03-19 16:37 ` Mark Brown [this message]
2012-03-19 16:37 ` Mark Brown
2012-03-21 17:22 ` Kumar Gala
2012-03-21 17:22 ` Kumar Gala
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=20120319163742.GE5132@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.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.