netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: David S Miller <davem@redhat.com>, netdev@oss.sgi.com
Subject: Re: [PATCH] rearrange frto field to save space.
Date: Wed, 21 Apr 2004 17:15:12 -0700	[thread overview]
Message-ID: <1082592912.11328.0.camel@localhost.localdomain> (raw)
In-Reply-To: <20040421111032.0705b605@dell_ss3.pdx.osdl.net>

On Wed, 2004-04-21 at 11:10, Stephen Hemminger wrote:
> +	__u8	unused_pad;

There's no real reason that I can see to have padding here.

  parent reply	other threads:[~2004-04-22  0:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040420155738.4146b5bb.davem@redhat.com>
2004-04-21 18:10 ` [PATCH] rearrange frto field to save space Stephen Hemminger
2004-04-21 23:59   ` David S. Miller
2004-04-22  0:15   ` Joe Perches [this message]
2004-04-22  0:38     ` David S. Miller
2004-04-21 18:10 ` [PATCH] add sysctl to turn off caching metrics Stephen Hemminger
2004-04-22  0:01   ` David S. 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=1082592912.11328.0.camel@localhost.localdomain \
    --to=joe@perches.com \
    --cc=davem@redhat.com \
    --cc=netdev@oss.sgi.com \
    --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).