From: Chris Leech <christopher.leech@intel.com>
To: David Miller <davem@davemloft.net>
Cc: "sam@ravnborg.org" <sam@ravnborg.org>,
netdev@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net headers: export dcbnl.h
Date: Fri, 27 Feb 2009 10:16:01 -0800 [thread overview]
Message-ID: <1235758561.4774.25.camel@cleech-mobl1> (raw)
In-Reply-To: <20090227.024635.51509388.davem@davemloft.net>
On Fri, 2009-02-27 at 02:46 -0800, David Miller wrote:
> From: Sam Ravnborg <sam@ravnborg.org>
> Date: Fri, 27 Feb 2009 06:55:06 +0100
>
> > On Thu, Feb 26, 2009 at 04:46:35PM -0800, Chris Leech wrote:
> > > The DCB netlink interface is required for building the userspace tools
> > > available at e1000.sourceforge.net
> >
> > Hmmm, is that file ready for export....
> >
> > >From dcbnl.h:
> > #ifndef __LINUX_DCBNL_H__
> > #define __LINUX_DCBNL_H__
> >
> > #define DCB_PROTO_VERSION 1
> >
> > struct dcbmsg {
> > unsigned char dcb_family;
> > __u8 cmd;
> > __u16 dcb_pad;
> > };
> >
> > 1) It uses __u8/__u16 so it would be nice it is included <linux/types.h>
> > so these are actually defined.
OK, I'll send again with a patch to add <linux/types.h>
> > 2) Why does it use "unsigned char" for one member and __u8 for another.
> > It looks inconsistent.
My guess is that the first member was made to be unsigned char to match
struct rtgenmsg, but other rtnetlink users define family as __u8
(fib_rule_hdr, ndmsg, ndtmsg) so it should be OK to change it.
> > We export headers that are much worse but we better raise the bar a little.
>
> Agreed, we should sort out these issues before exporting.
prev parent reply other threads:[~2009-02-27 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 0:46 [PATCH] net headers: export dcbnl.h Chris Leech
2009-02-27 5:55 ` Sam Ravnborg
2009-02-27 10:46 ` David Miller
2009-02-27 18:16 ` Chris Leech [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=1235758561.4774.25.camel@cleech-mobl1 \
--to=christopher.leech@intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sam@ravnborg.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