From: Francois Romieu <romieu@cogenit.fr>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org, khc@pm.waw.pl, davem@redhat.com,
torvalds@transmeta.com
Subject: Re: [PATCH] HDLC patch for 2.5.5 (1/3)
Date: Mon, 18 Feb 2002 09:57:38 +0100 [thread overview]
Message-ID: <20020218095738.A7530@fafner.intra.cogenit.fr> (raw)
In-Reply-To: <20020217193051.C14629@se1.cogenit.fr> <3C703C36.A7579B72@mandrakesoft.com>
In-Reply-To: <3C703C36.A7579B72@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Sun, Feb 17, 2002 at 06:26:46PM -0500
Jeff Garzik <jgarzik@mandrakesoft.com> :
> Francois Romieu wrote:
> >
> > [1/3]:
> > - struct if_settings in struct ifreq becomes struct if_settings *
>
> mostly ok... I'm wondering how this specific item (shown below in the
> patch portion quoted) affects binary compatibility... how does this
> affect userland if ifru_settings is suddenly a pointer?
2.4.18-preX:include/linux/if.h
[...]
union {
struct sockaddr ifru_addr;
struct sockaddr ifru_dstaddr;
struct sockaddr ifru_broadaddr;
struct sockaddr ifru_netmask;
struct sockaddr ifru_hwaddr;
short ifru_flags;
int ifru_ivalue;
int ifru_mtu;
struct ifmap ifru_map;
char ifru_slave[IFNAMSIZ]; /* Just fits the size */
char ifru_newname[IFNAMSIZ];
char * ifru_data; <-- Nothing after this field.
} ifr_ifru;
};
The member ifru_settings is added to the union by Krzysztof's patch.
Existing userland (Krzysztof's new utility aside) shouldn't matter as
- it ignores this member;
- the member doesn't make the union bigger (Krzysztof noticed my previous
patch choked on this).
If nobody does it before, the utility will be modified when I feel like it's
time to test the code. Shouldn't be long (TM).
--
Ueimor
prev parent reply other threads:[~2002-02-18 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-17 18:30 Francois Romieu
2002-02-17 23:26 ` Jeff Garzik
2002-02-18 8:57 ` Francois Romieu [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=20020218095738.A7530@fafner.intra.cogenit.fr \
--to=romieu@cogenit.fr \
--cc=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®