From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: davem@davemloft.net, linux-sctp@vger.kernel.org,
lksctp-developers@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH 2/5] [SCTP]: "list_for_each()" -> "list_for_each_entry()" where appropriate.
Date: Thu, 10 Apr 2008 15:55:53 -0400 [thread overview]
Message-ID: <47FE70C9.3070009@hp.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0804101545570.24254@localhost.localdomain>
Robert P. J. Day wrote:
> actually, if i remember correctly, davem rejected that change as
> being too disruptive at the moment, no?
>
> rday
> --
>
> ========================================================================
> Robert P. J. Day
> Linux Consulting, Training and Annoying Kernel Pedantry:
> Have classroom, will lecture.
>
> http://crashcourse.ca Waterloo, Ontario, CANADA
> ========================================================================
>
this is for 2.6.26, which should be fine. it was too disruptive for net.26.
-vlad
next prev parent reply other threads:[~2008-04-10 19:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 19:39 [PATCH 2.6.26] [SCTP] SCTP cleanups Vlad Yasevich
2008-04-10 19:39 ` [PATCH 1/5] [SCTP] Correct /proc/net/assocs formatting error Vlad Yasevich
2008-04-10 19:39 ` [PATCH 2/5] [SCTP]: "list_for_each()" -> "list_for_each_entry()" where appropriate Vlad Yasevich
2008-04-10 19:46 ` Robert P. J. Day
2008-04-10 19:55 ` Vlad Yasevich [this message]
2008-04-10 22:36 ` David Miller
2008-04-10 23:07 ` Robert P. J. Day
2008-04-10 19:39 ` [PATCH 3/5] [SCTP]: Remove an unused parameter from sctp_cmd_hb_timer_update Vlad Yasevich
2008-04-10 19:39 ` [PATCH 4/5] MAINTAINERS: New sctp mailing list Vlad Yasevich
2008-04-10 22:35 ` [PATCH 2.6.26] [SCTP] SCTP cleanups David Miller
2008-04-11 12:41 ` Vlad Yasevich
2008-04-13 2:03 ` David Miller
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=47FE70C9.3070009@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--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 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).