From: David Miller <davem@davemloft.net>
To: vapier@gentoo.org
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] linux/atm_tcp.h: cleanup for userspace
Date: Wed, 23 Apr 2008 19:24:18 -0700 (PDT) [thread overview]
Message-ID: <20080423.192418.188020745.davem@davemloft.net> (raw)
In-Reply-To: <1208661754-3197-1-git-send-email-vapier@gentoo.org>
From: Mike Frysinger <vapier@gentoo.org>
Date: Sat, 19 Apr 2008 23:22:34 -0400
> The atm_tcp.h uses types from linux/atm.h, but does not include it. It
> should also use the standard __u## types from linux/types.h rather than the
> uint##_t types since the former can be found with the kernel already.
>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
I don't think this is a sufficient patch to solve these problems.
> @@ -8,10 +8,8 @@
> #define LINUX_ATM_TCP_H
>
> #include <linux/atmapi.h>
> -
> -#ifdef __KERNEL__
> #include <linux/types.h>
> -#endif
> +#include <linux/atm.h>
> #include <linux/atmioc.h>
>
>
So you're adding linux/atm.h as an include for non-kernel, fine,
but:
> @@ -20,9 +18,9 @@
> */
>
> struct atmtcp_hdr {
> - uint16_t vpi;
> - uint16_t vci;
> - uint32_t length; /* ... of data part */
> + __u16 vpi;
> + __u16 vci;
> + __u32 length; /* ... of data part */
> };
>
> /*
Well, linux/atm.h, which we'll now get, has the same exact problem,
it uses "uint16_t" and related types.
Futehermore, nothing in the include chain will get linux/types.h
include, which we'll need. linux/atm.h protects the inclusion
of linux/types.h with __KERNEL__.
next prev parent reply other threads:[~2008-04-24 2:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 3:22 Mike Frysinger
2008-04-24 2:24 ` David Miller [this message]
2008-04-24 3:03 ` Mike Frysinger
2008-04-24 3:18 ` David Miller
2008-04-24 3:33 ` Mike Frysinger
2008-04-24 4:23 ` 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=20080423.192418.188020745.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier@gentoo.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
all inboxes | Powered by JetHome®