From: "Jiří Župka" <jzupka@redhat.com>
To: netdev@vger.kernel.org
Cc: loke.chetan@gmail.com, davem@davemloft.net, jpirko@redhat.com,
"Jiří Župka" <jzupka@redhat.com>
Subject: [patch net-next-2.6] Repair wrong named definition aligned_u64
Date: Fri, 30 Sep 2011 14:09:54 +0200 [thread overview]
Message-ID: <1317384594-17014-1-git-send-email-jzupka@redhat.com> (raw)
This repairs problem with compile library in userspace (libnl).
Signed-off-by: Jiří Župka <jzupka@redhat.com>
---
include/linux/if_packet.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/linux/if_packet.h b/include/linux/if_packet.h
index 5e76988..f379929 100644
--- a/include/linux/if_packet.h
+++ b/include/linux/if_packet.h
@@ -173,7 +173,7 @@ struct tpacket_hdr_v1 {
* you can see which blk[s] is[are] outstanding etc.
* 3. Validate kernel code.
*/
- aligned_u64 seq_num;
+ __aligned_u64 seq_num;
/*
* ts_last_pkt:
--
1.7.6.4
next reply other threads:[~2011-09-30 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 12:09 Jiří Župka [this message]
2011-10-03 18:04 ` [patch net-next-2.6] Repair wrong named definition aligned_u64 David 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=1317384594-17014-1-git-send-email-jzupka@redhat.com \
--to=jzupka@redhat.com \
--cc=davem@davemloft.net \
--cc=jpirko@redhat.com \
--cc=loke.chetan@gmail.com \
--cc=netdev@vger.kernel.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).