From: David Miller <davem@davemloft.net>
To: dborkman@redhat.com
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: Re: [PATCH net-next 0/9] Minor SCTP cleanups all over the place
Date: Wed, 17 Apr 2013 14:13:21 -0400 (EDT) [thread overview]
Message-ID: <20130417.141321.1161500597576212704.davem@davemloft.net> (raw)
In-Reply-To: <1366146438-8815-1-git-send-email-dborkman@redhat.com>
From: Daniel Borkmann <dborkman@redhat.com>
Date: Tue, 16 Apr 2013 23:07:09 +0200
> That's a batch of cleanups for the SCTP protocol. Probably all
> deadly boring and trivial patches, but it always bugs me. :-) I
> guess this is still from the very SCTP beginning in Linux. Well,
> at least we can now remove 41 lines of code in total. lksctp-tools
> test suite run through without problems.
>
> Daniel Borkmann (9):
> net: sctp: sctp_ssnmap: remove 'malloced' element from struct
> net: sctp: sctp_inq: remove dead code
> net: sctp: sctp_outq: remove 'malloced' from its struct
> net: sctp: sctp_outq: consolidate chars into bitfield
> net: sctp: outqueue: simplify sctp_outq_uncork function
> net: sctp: sctp_transport: remove unused variable
> net: sctp: sctp_bind_addr: remove dead code
> net: sctp: sctp_ulpq: remove 'malloced' struct member
> net: sctp: sctp_ulpq: do not use char as a struct member
All applied except for #4 and #9, thanks.
next prev parent reply other threads:[~2013-04-17 18:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 21:07 [PATCH net-next 0/9] Minor SCTP cleanups all over the place Daniel Borkmann
2013-04-16 21:07 ` [PATCH net-next 1/9] net: sctp: sctp_ssnmap: remove 'malloced' element from struct Daniel Borkmann
2013-04-17 12:45 ` Neil Horman
2013-04-17 12:52 ` Daniel Borkmann
2013-04-17 17:17 ` Daniel Borkmann
2013-04-17 19:18 ` Neil Horman
2013-04-16 21:07 ` [PATCH net-next 2/9] net: sctp: sctp_inq: remove dead code Daniel Borkmann
2013-04-17 12:47 ` Neil Horman
2013-04-16 21:07 ` [PATCH net-next 3/9] net: sctp: sctp_outq: remove 'malloced' from its struct Daniel Borkmann
2013-04-17 12:57 ` Neil Horman
2013-04-16 21:07 ` [PATCH net-next 4/9] net: sctp: sctp_outq: consolidate chars into bitfield Daniel Borkmann
2013-04-17 8:43 ` David Laight
2013-04-17 9:26 ` Daniel Borkmann
2013-04-17 15:27 ` Neil Horman
2013-04-17 15:35 ` Vlad Yasevich
2013-04-17 15:40 ` Neil Horman
2013-04-17 15:38 ` Daniel Borkmann
2013-04-17 15:44 ` Vlad Yasevich
2013-04-17 15:31 ` Neil Horman
2013-04-16 21:07 ` [PATCH net-next 5/9] net: sctp: outqueue: simplify sctp_outq_uncork function Daniel Borkmann
2013-04-17 15:32 ` Neil Horman
2013-04-16 21:07 ` [PATCH net-next 6/9] net: sctp: sctp_transport: remove unused variable Daniel Borkmann
2013-04-17 15:34 ` Neil Horman
2013-04-16 21:07 ` [PATCH net-next 7/9] net: sctp: sctp_bind_addr: remove dead code Daniel Borkmann
2013-04-17 15:35 ` Neil Horman
2013-04-16 21:07 ` [PATCH net-next 8/9] net: sctp: sctp_ulpq: remove 'malloced' struct member Daniel Borkmann
2013-04-17 15:46 ` Neil Horman
2013-04-16 21:07 ` [PATCH net-next 9/9] net: sctp: sctp_ulpq: do not use char as a " Daniel Borkmann
2013-04-17 15:36 ` Vlad Yasevich
2013-04-17 15:41 ` Daniel Borkmann
2013-04-17 15:45 ` Neil Horman
2013-04-17 16:28 ` David Laight
2013-04-17 18:13 ` David Miller [this message]
2013-04-17 18:55 ` [PATCH net-next 0/9] Minor SCTP cleanups all over the place Daniel Borkmann
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=20130417.141321.1161500597576212704.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=linux-sctp@vger.kernel.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).