netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Hagen Paul Pfeifer <hagen@jauu.net>,
	Rainer Baumann <baumann@tik.ee.ethz.ch>,
	Stephen Hemminger <shemminger@osdl.org>,
	netdev@VGER.KERNEL.ORG, netem@osdl.org
Subject: Re: [PATCH 2.6.18 2/2] LARTC: trace control for netem: kernelspace
Date: Sat, 16 Dec 2006 22:11:47 +0100	[thread overview]
Message-ID: <20061216211147.GA4853@c3po.0xdef.net> (raw)
In-Reply-To: <20061216151141.GB3641@c3po.0xdef.net>


>This patch isn't ok ( maybe this patch benefit from gcc padding behaviours):

Ignore this - I thought this function returns a pointer ... 
(take a look at my email signature :-)

HGN



-- 
COFFEE.EXE Missing - Insert Cup and Press Any Key. 


      reply	other threads:[~2006-12-16 21:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-15 10:39 [PATCH 2.6.18 2/2] LARTC: trace control for netem: kernelspace Rainer Baumann
2006-12-16 15:11 ` Hagen Paul Pfeifer
2006-12-16 21:11   ` Hagen Paul Pfeifer [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=20061216211147.GA4853@c3po.0xdef.net \
    --to=hagen@jauu.net \
    --cc=baumann@tik.ee.ethz.ch \
    --cc=netdev@VGER.KERNEL.ORG \
    --cc=netem@osdl.org \
    --cc=shemminger@osdl.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).