From: David Miller <davem@davemloft.net>
To: paul.gortmaker@windriver.com
Cc: netdev@vger.kernel.org, allan.stephens@windriver.com
Subject: Re: [PATCH net-next 0/16] tipc: 1st integration of basic changes from sourceforge
Date: Wed, 12 May 2010 23:28:43 -0700 (PDT) [thread overview]
Message-ID: <20100512.232843.226760771.davem@davemloft.net> (raw)
In-Reply-To: <1273624218-22514-1-git-send-email-paul.gortmaker@windriver.com>
From: Paul Gortmaker <paul.gortmaker@windriver.com>
Date: Tue, 11 May 2010 20:30:02 -0400
> The following patches are step one in making use of the changes that
> were stored away on sourceforge but not yet integrated into the kernel.
>
> Since I am far from knowledgeable on tipc, this starts by pulling in
> the 1st batch of basic/cosmetic changes that will at least start to
> reduce the delta between the two. Hopefully getting all the simple
> stuff out of the way 1st will help clarify what is left of interest.
>
> I've also put the same commits on the branch tipc-May11_2010 in:
> git://git.kernel.org/pub/scm/linux/kernel/git/paulg/net-next-2.6.git
> in case that is more convenient for people.
All applied to net-next-2.6, thanks for doing this work Paul.
prev parent reply other threads:[~2010-05-13 6:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 0:30 [PATCH net-next 0/16] tipc: 1st integration of basic changes from sourceforge Paul Gortmaker
2010-05-12 0:30 ` [PATCH net-next 01/16] tipc: Eliminate obsolete port's "congested_link" field Paul Gortmaker
2010-05-12 0:30 ` [PATCH net-next 02/16] tipc: Eliminate unused argument in print statement Paul Gortmaker
2010-05-12 0:30 ` [PATCH net-next 03/16] tipc: Prune unused data structures from configuration service Paul Gortmaker
2010-05-12 0:30 ` [PATCH net-next 04/16] tipc: Eliminate unnecessary initialization in native API send routines Paul Gortmaker
2010-05-12 0:30 ` [PATCH net-next 05/16] tipc: Rename "multicast-link" to "broadcast-link" Paul Gortmaker
2010-05-12 0:30 ` [PATCH net-next 06/16] tipc: Add support for "-s" configuration option Paul Gortmaker
2010-05-12 0:30 ` [PATCH net-next 07/16] tipc: Update commenting in TIPC API Paul Gortmaker
2010-05-12 0:30 ` [PATCH net-next 08/16] tipc: remove abstraction for link_max_pkt Paul Gortmaker
2010-05-12 0:30 ` [PATCH net-next 09/16] tipc: Relocate trivial link status functions to header file Paul Gortmaker
2010-05-12 0:30 ` [PATCH net-next 10/16] tipc: add tipc_ prefix to fcns targeted for un-inlining Paul Gortmaker
2010-05-12 0:30 ` [PATCH net-next 11/16] tipc: Reduce footprint by un-inlining address routines Paul Gortmaker
2010-05-12 0:30 ` [PATCH net-next 12/16] tipc: Reduce footprint by un-inlining nmap routines Paul Gortmaker
2010-05-12 0:30 ` [PATCH net-next 13/16] tipc: Reduce footprint by un-inlining port list routines Paul Gortmaker
2010-05-12 0:30 ` [PATCH net-next 14/16] tipc: Reduce footprint by un-inlining bearer congestion routine Paul Gortmaker
2010-05-12 0:30 ` [PATCH net-next 15/16] tipc: Reduce footprint by un-inlining buf_acquire routine Paul Gortmaker
2010-05-12 0:30 ` [PATCH net-next 16/16] tipc: Reduce footprint by un-inlining tipc_msg_* routines Paul Gortmaker
2010-05-13 6:28 ` 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=20100512.232843.226760771.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=allan.stephens@windriver.com \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.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).