From: David Miller <davem@davemloft.net>
To: timur@freescale.com
Cc: avorontsov@ru.mvista.com, afleming@freescale.com,
leoli@freescale.com, galak@kernel.crashing.org,
netdev@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/3] ucc_geth: Rearrange some code to avoid forward declarations
Date: Fri, 11 Sep 2009 12:19:50 -0700 (PDT) [thread overview]
Message-ID: <20090911.121950.207367910.davem@davemloft.net> (raw)
In-Reply-To: <4AA8F880.1000300@freescale.com>
From: Timur Tabi <timur@freescale.com>
Date: Thu, 10 Sep 2009 08:00:48 -0500
> Anton Vorontsov wrote:
>> We'll need ugeth_disable() and ugeth_enable() calls earlier in the
>> file, so rearrange some code to avoid forward declarations.
>>
>> The patch doesn't contain any functional changes.
>>
>> Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
>
> Acked-by: Timur Tabi <timur@freescale.com>
Applied.
prev parent reply other threads:[~2009-09-11 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 2:01 [PATCH 2/3] ucc_geth: Rearrange some code to avoid forward declarations Anton Vorontsov
2009-09-10 13:00 ` Timur Tabi
2009-09-11 19:19 ` David Miller [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=20090911.121950.207367910.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=afleming@freescale.com \
--cc=avorontsov@ru.mvista.com \
--cc=galak@kernel.crashing.org \
--cc=leoli@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.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).