From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: "David S. Miller" <davem@redhat.com>,
Bart De Schuymer <bdschuym@pandora.be>
Cc: netfilter-devel@lists.netfilter.org, netdev@oss.sgi.com
Subject: [PATCH] [bdschuym@pandora.be: Re: ipt_physdev.c alignment problems on parisc64]
Date: Wed, 3 Sep 2003 13:20:23 -0300 [thread overview]
Message-ID: <20030903162022.GI6405@conectiva.com.br> (raw)
Bart,
Yes, it makes ipt_pysdev.c compile on parisc, Dave, could you please
apply it? Or perhaps wait for the netfilter patches, your call.
- Arnaldo
----- Forwarded message from Bart De Schuymer <bdschuym@pandora.be> -----
Date: Tue, 2 Sep 2003 21:16:41 +0200
From: Bart De Schuymer <bdschuym@pandora.be>
Subject: Re: ipt_physdev.c alignment problems on parisc64
To: Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
netfilter-devel@lists.netfilter.org
Cc: Linux Networking Development Mailing List <netdev@oss.sgi.com>
On Tuesday 02 September 2003 16:30, Arnaldo Carvalho de Melo wrote:
> The 1.786.1.54 changeset (i.e. the initial ipt_physdev.c one 8) created
Does this fix it?
cheers,
Bart
--- linux-2.6.0-test4/include/linux/netfilter_ipv4/ipt_physdev.h.old 2003-09-02 21:11:12.000000000 +0200
+++ linux-2.6.0-test4/include/linux/netfilter_ipv4/ipt_physdev.h 2003-09-02 21:12:30.000000000 +0200
@@ -15,7 +15,7 @@
struct ipt_physdev_info {
u_int8_t invert;
u_int8_t bitmask;
- char physindev[IFNAMSIZ];
+ char physindev[IFNAMSIZ] __attribute__ ((aligned (__alignof__(unsigned long))));
char in_mask[IFNAMSIZ];
char physoutdev[IFNAMSIZ];
char out_mask[IFNAMSIZ];
----- End forwarded message -----
next reply other threads:[~2003-09-03 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 16:20 Arnaldo Carvalho de Melo [this message]
2003-09-04 3:05 ` [PATCH] [bdschuym@pandora.be: Re: ipt_physdev.c alignment problems on parisc64] 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=20030903162022.GI6405@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=bdschuym@pandora.be \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@lists.netfilter.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).