From: Kumar Gala <galak@kernel.crashing.org>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] Rename ucc_slow_info.us_regs to .regs
Date: Thu, 8 Feb 2007 11:11:27 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.64.0702081111110.29459@localhost.localdomain> (raw)
In-Reply-To: <1170953251140-git-send-email-timur@freescale.com>
On Thu, 8 Feb 2007, Timur Tabi wrote:
> Rename the 'us_regs' field of the ucc_slow_info structure in ucc_slow.h
> to just 'regs'. The equivalent field in the ucc_fast_info structure is
> also called 'regs', so this patch makes them comparable, and makes the
> code a little easier to read, because there already is a 'us_regs' in
> another ucc_slow structure.
>
> Signed-off-by: Timur Tabi <timur@freescale.com>
> ---
applied
- k
next prev parent reply other threads:[~2007-02-08 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 16:47 [PATCH] Rename ucc_slow_info.us_regs to .regs Timur Tabi
2007-02-08 17:11 ` Kumar Gala [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-08 16:32 Timur Tabi
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.0702081111110.29459@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).