From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
allan.stephens@windriver.com
Subject: Re: [PATCH net-next 5/5] tipc: clean out all instances of #if 0'd unused code
Date: Wed, 13 Oct 2010 13:08:43 -0400 [thread overview]
Message-ID: <4CB5E79B.4060507@windriver.com> (raw)
In-Reply-To: <20101013162652.GF31379@hmsreliant.think-freely.org>
On 10-10-13 12:26 PM, Neil Horman wrote:
> On Tue, Oct 12, 2010 at 08:25:58PM -0400, Paul Gortmaker wrote:
>> Remove all instances of legacy, or as yet to be implemented code
>> that is currently living within an #if 0 ... #endif block.
>> In the rare instance that some of it be needed in the future,
>> it can still be dragged out of history, but there is no need
>> for it to sit in mainline.
>>
>> Signed-off-by: Paul Gortmaker<paul.gortmaker@windriver.com>
> Acked-by: Neil Horman<nhorman@tuxdriver.com>
>
Thanks for all the reviews. As I'd indicated a while back, I
am by far no TIPC expert, so it may take me a bit to digest
it and rework things on 1 --> 4. That will probably put them
into the "for-38" net-next timeframe, as I'm guessing net-next
that is destined for 2.6.37 will close in a day or two.
This cleanup patch (patch #5) doesn't explicitly depend on
the other 4 bearer related patches, so it can be applied
at whatever time is most convenient for Dave.
Paul.
next prev parent reply other threads:[~2010-10-13 17:08 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 0:25 [PATCH net-next 1/5] tipc: Enhance enabling and disabling of Ethernet bearers Paul Gortmaker
2010-10-13 0:25 ` [PATCH net-next 2/5] tipc: Simplify bearer shutdown logic Paul Gortmaker
2010-10-13 14:39 ` Neil Horman
2010-10-14 23:58 ` Paul Gortmaker
2010-10-15 10:48 ` Neil Horman
2010-10-13 0:25 ` [PATCH net-next 3/5] tipc: Optimizations to bearer enabling logic Paul Gortmaker
2010-10-13 14:58 ` Neil Horman
2010-10-15 1:11 ` Paul Gortmaker
2010-10-15 11:00 ` Neil Horman
2010-10-15 21:31 ` Paul Gortmaker
2010-10-18 10:50 ` Neil Horman
2010-10-18 21:43 ` Paul Gortmaker
2010-10-18 23:59 ` Neil Horman
2010-10-21 11:31 ` David Miller
2010-10-13 0:25 ` [PATCH net-next 4/5] tipc: Rework data structures that track neighboring nodes and links Paul Gortmaker
2010-10-13 16:24 ` Neil Horman
2010-10-13 0:25 ` [PATCH net-next 5/5] tipc: clean out all instances of #if 0'd unused code Paul Gortmaker
2010-10-13 16:26 ` Neil Horman
2010-10-13 17:08 ` Paul Gortmaker [this message]
2010-10-13 17:23 ` Neil Horman
2010-10-13 21:28 ` David Miller
2010-10-13 23:20 ` [PATCH net-next] tipc: cleanup function namespace Stephen Hemminger
2010-10-14 0:23 ` Paul Gortmaker
2010-10-14 0:32 ` Stephen Hemminger
2010-10-14 1:29 ` Neil Horman
2010-10-14 17:53 ` Paul Gortmaker
2010-10-14 18:33 ` Stephen Hemminger
2010-10-14 19:49 ` Jon Maloy
2010-10-14 21:44 ` Paul Gortmaker
2010-10-14 22:13 ` Stephen Hemminger
2010-10-15 11:01 ` Neil Horman
2010-10-15 16:59 ` Jon Maloy
2010-10-14 13:31 ` Jon Maloy
2010-10-16 18:56 ` David Miller
2010-10-13 13:42 ` [PATCH net-next 1/5] tipc: Enhance enabling and disabling of Ethernet bearers Neil Horman
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=4CB5E79B.4060507@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=allan.stephens@windriver.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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).