From: "Timur Tabi" <timur@freescale.com>
To: "Anton Vorontsov" <avorontsov@ru.mvista.com>
Cc: netdev@vger.kernel.org, linuxppc-dev@ozlabs.org,
Andy Fleming <afleming@freescale.com>,
Li Yang <leoli@freescale.com>, Jeff Garzik <jgarzik@pobox.com>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH 6/6] ucc_geth: Remove UGETH_FILTERING dead code
Date: Sat, 20 Dec 2008 21:23:06 -0600 [thread overview]
Message-ID: <ed82fe3e0812201923s7ff3401i2d12aca4ae9de1e7@mail.gmail.com> (raw)
In-Reply-To: <20081218182335.GF30682@oksana.dev.rtsoft.ru>
On Thu, Dec 18, 2008 at 12:23 PM, Anton Vorontsov
<avorontsov@ru.mvista.com> wrote:
> The code appears to be dead: nobody call these functions, plus build
> breaks when UGETH_FILTERING is enabled:
I general, I agree with patches like this, but I'd like to hear from
Leo first why this code was written in the first place before I can
ack it.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-12-21 3:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 18:23 [PATCH 6/6] ucc_geth: Remove UGETH_FILTERING dead code Anton Vorontsov
2008-12-21 3:23 ` Timur Tabi [this message]
2008-12-22 11:13 ` Li Yang
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=ed82fe3e0812201923s7ff3401i2d12aca4ae9de1e7@mail.gmail.com \
--to=timur@freescale.com \
--cc=afleming@freescale.com \
--cc=avorontsov@ru.mvista.com \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=leoli@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).