From: David Miller <davem@davemloft.net>
To: xemul@openvz.org
Cc: netdev@vger.kernel.org, devel@openvz.org
Subject: Re: [PATCH] Use list_head-s in inetpeer.c
Date: Mon, 12 Nov 2007 01:42:17 -0800 (PST) [thread overview]
Message-ID: <20071112.014217.62497023.davem@davemloft.net> (raw)
In-Reply-To: <47381573.5020506@openvz.org>
From: Pavel Emelyanov <xemul@openvz.org>
Date: Mon, 12 Nov 2007 11:57:23 +0300
> No. I remove _two_ pointers unused_next and unused_prevp, and add
> the list_head, which is _two_ pointers as well. I've even checked the
> compilation on both i386 and x86_64 - the sizeof(struct inet_peer)
> is not changed.
>
> You must have overlooked the unused_prevp member, because it is
> declared in the same line as the unused_next. Or I miss something else?
I missed that, please resubmit your patch.
Thanks.
prev parent reply other threads:[~2007-11-12 9:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 14:32 [PATCH] Use list_head-s in inetpeer.c Pavel Emelyanov
2007-11-11 5:31 ` David Miller
2007-11-12 8:57 ` Pavel Emelyanov
2007-11-12 9:42 ` 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=20071112.014217.62497023.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=devel@openvz.org \
--cc=netdev@vger.kernel.org \
--cc=xemul@openvz.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).