From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, lksctp-developers@lists.sourceforge.net,
rpjday@crashcourse.ca
Subject: Re: [PATCH 1/4] [SCTP]: "list_for_each()" -> "list_for_each_entry()" where appropriate.
Date: Fri, 28 Mar 2008 20:59:27 -0400 [thread overview]
Message-ID: <47ED946F.9070209@hp.com> (raw)
In-Reply-To: <20080328.163218.258439481.davem@davemloft.net>
David Miller wrote:
> From: Vlad Yasevich <vladislav.yasevich@hp.com>
> Date: Fri, 28 Mar 2008 10:56:17 -0400
>
>> From: Robert P. J. Day <rpjday@crashcourse.ca>
>>
>> Replacing (almost) all invocations of list_for_each() with
>> list_for_each_entry() tightens up the code and allows for the deletion
>> of numerous list iterator variables that are no longer necessary.
>>
>> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>> Signed-off-by: Vlad Yasevich <vladislav.yasevich@hp.com>
>
> This is not a "bug fix", it's a huge cleanup and thus not appropriate
> for 2.6.x
>
> Please rebuild this patch series without this patch included,
> you can submit it for 2.6.26
>
Sorry about that, you are right. Will do.
-vlad
next prev parent reply other threads:[~2008-03-29 0:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 14:56 [GIT PATCHES 0/4] SCTP fixes Vlad Yasevich
2008-03-28 14:56 ` [PATCH 1/4] [SCTP]: "list_for_each()" -> "list_for_each_entry()" where appropriate Vlad Yasevich
2008-03-28 23:32 ` David Miller
2008-03-29 0:59 ` Vlad Yasevich [this message]
2008-03-28 14:56 ` [PATCH 2/4] [SCTP]: Add check for hmac_algo parameter in sctp_verify_param() Vlad Yasevich
2008-03-28 14:56 ` [PATCH 3/4] [SCTP]: Fix protocol violation when receiving an error lenght INIT-ACK Vlad Yasevich
2008-03-28 14:56 ` [PATCH 4/4] [SCTP]: Remove an unused parameter from sctp_cmd_hb_timer_update Vlad Yasevich
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=47ED946F.9070209@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=davem@davemloft.net \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.