From: acme@ghostprotocols.net (Arnaldo Carvalho de Melo)
To: "YOSHIFUJI Hideaki / ?$B5HF#1QL@" <yoshfuji@linux-ipv6.org>
Cc: ahendry@tusc.com.au, eis@baty.hanse.de,
linux-x25@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] X25: Add ITU-T facilites
Date: Tue, 18 Oct 2005 13:37:02 -0200 [thread overview]
Message-ID: <20051018153702.GC23167@mandriva.com> (raw)
In-Reply-To: <20051018.152318.68554424.yoshfuji@linux-ipv6.org>
Em Tue, Oct 18, 2005 at 03:23:18PM +0900, YOSHIFUJI Hideaki / ?$B5HF#1QL@ escreveu:
> In article <1129615767.3695.15.camel@localhost.localdomain> (at Tue, 18 Oct 2005 16:09:27 +1000), Andrew Hendry <ahendry@tusc.com.au> says:
>
> > +/*
> > +* ITU DTE facilities
> > +* Only the called and calling address
> > +* extension are currently implemented.
> > +* The rest are in place to avoid the struct
> > +* changing size if someone needs them later
> > ++ */
> > +struct x25_dte_facilities {
> > + unsigned int calling_len, called_len;
> > + char calling_ae[20];
> > + char called_ae[20];
> > + unsigned char min_throughput;
> > + unsigned short delay_cumul;
> > + unsigned short delay_target;
> > + unsigned short delay_max;
> > + unsigned char expedited;
> > +};
>
> Why don't you use fixed size members?
> And we can eliminate 8bit hole.
>
> struct x25_dte_facilities {
> u32 calling_len
> u32 called_len;
I guess the two above can be 'u8' as they refer to calling_ae and called_ae
that at most will be '20'?
> u8 calling_ae[20];
> u8 called_ae[20];
- Arnaldo
next prev parent reply other threads:[~2005-10-18 15:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 1:47 [PATCH] X25: Add ITU-T facilites Andrew Hendry
2005-10-17 2:28 ` Arnaldo Carvalho de Melo
2005-10-18 6:09 ` Andrew Hendry
2005-10-18 6:23 ` YOSHIFUJI Hideaki / 吉藤英明
2005-10-18 15:37 ` Arnaldo Carvalho de Melo [this message]
2005-10-18 15:48 ` linux-os (Dick Johnson)
2005-10-18 15:48 ` linux-os (Dick Johnson)
2005-10-20 1:10 ` Andrew Hendry
2005-10-20 7:41 ` Bernd Jendrissek
2005-10-20 12:30 ` Arnd Bergmann
2005-10-24 1:01 ` Andrew Hendry
-- strict thread matches above, loose matches on Subject: below --
2005-10-17 1:27 Andrew Hendry
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=20051018153702.GC23167@mandriva.com \
--to=acme@ghostprotocols.net \
--cc=ahendry@tusc.com.au \
--cc=eis@baty.hanse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-x25@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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 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.