From: Kumar Gala <galak@kernel.crashing.org>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] qe: ucc_slow.guemr is in the wrong place
Date: Thu, 29 Mar 2007 14:43:55 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0703291443420.23408@localhost.localdomain> (raw)
In-Reply-To: <1174937142750-git-send-email-timur@freescale.com>
On Mon, 26 Mar 2007, Timur Tabi wrote:
> The definition of struct ucc_slow puts the guemr register immediately after the
> utpt register, when it should be at offset 0x90. This patch adds the missing
> 0x52-byte padding.
>
> Signed-off-by: Timur Tabi <timur@freescale.com>
> ---
> include/asm-powerpc/immap_qe.h | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
applied
- k
prev parent reply other threads:[~2007-03-29 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 19:25 [PATCH] qe: ucc_slow.guemr is in the wrong place Timur Tabi
2007-03-29 19:43 ` Kumar Gala [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=Pine.LNX.4.64.0703291443420.23408@localhost.localdomain \
--to=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 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).