Netdev List
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Kevin Curtis <Kevin.Curtis@farsite.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>,
	"Dermot Smith" <dermot.smith@farsite.com>
Subject: Re: [PATCH 002/007] WAN Drivers: Update farsync driver and introduce fsflex driver
Date: Wed, 18 Sep 2013 16:30:32 +0100	[thread overview]
Message-ID: <1379518232.1522.15.camel@bwh-desktop.uk.level5networks.com> (raw)
In-Reply-To: <E603DC592C92B54A89CEF6B0919A0B1CAAAA787DA1@SOLO.hq.farsitecommunications.com>

On Wed, 2013-09-18 at 11:11 +0100, Kevin Curtis wrote:
> Farsite Communications FarSync driver update
> 
> Patch 2 of 7
> 
> Introduce a new include file required by the fsflex driver.
> 
> Signed-off-by: Kevin Curtis <kevin.curtis@farsite.com>
> 
> ---
> 
> diff -uprN -X linux-3.10.1/Documentation/dontdiff linux-3.10.1/drivers/net/wan/uss_cmn.h linux-3.10.1_new/drivers/net/wan/uss_cmn.h
> --- linux-3.10.1/drivers/net/wan/uss_cmn.h      1970-01-01 01:00:00.000000000 +0100
> +++ linux-3.10.1_new/drivers/net/wan/uss_cmn.h  2013-08-30 11:30:36.766167447 +0100
> @@ -0,0 +1,492 @@
> +/*
> + *      FarSync driver for Linux
> + *
> + *      Copyright (C) 2001-2013 FarSite Communications Ltd.
> + *      www.farsite.com
> + *
> + *      This program is free software; you can redistribute it and/or
> + *      modify it under the terms of the GNU General Public License
> + *      as published by the Free Software Foundation; either version
> + *      2 of the License, or (at your option) any later version.
> + *
> + * File        : uss_cmn.h
> + *
> + * Description : FarSync Flex common header file, shared between oncard code
> + *               and Windows and Linux drivers.
> + *
> + *               NOTE: all parameters are in Little Endian format

Then they should be declared as __le32 or similar.

[...]
> +typedef enum _USS_COMMANDS 
[...]
> +} USS_COMMANDS;

Adding typedefs for user-defined types is deprecated.  And please use
lower-case type names.

[...]
> +/*****************************************************************************/
> +/* InterfaceRecord definition                                                */
> +/*                                                                           */
> +/* For use with:                                                             */
> +/*                                                                           */
> +/*   IoctlCodeReadInterfaceRecord,                                           */
> +/*   IoctlCodeFarSyncReadInterfaceRecord                                     */
> +/*                                                                           */
> +/*****************************************************************************/
> +typedef struct _INTERFACE_RECORD {
> +       int rx_frame_count;     /* incremented after each frame rx'd */
> +       int tx_max_fr_size_now; /* max available frame size av. now  */
> +       /* (changes after each Tx DevIoctl   */
> +       /* to DD or after Tx completed)      */
> +       int status_count;       /* How many status events have been  */
> +       /* triggered.                        */
> +       u8 v24_in;              /* Last 'getv24 i/p' value got       */
> +       u8 v24_out;             /* Last 'setv24 o/p' value set       */
[...]

I think explicit padding is needed between v24_out and status_array.
Not all architectures require 32-bit words to be 32-bit aligned.

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

      parent reply	other threads:[~2013-09-18 15:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 10:11 [PATCH 002/007] WAN Drivers: Update farsync driver and introduce fsflex driver Kevin Curtis
2013-09-18 15:25 ` Joe Perches
2013-09-18 15:30 ` Ben Hutchings [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=1379518232.1522.15.camel@bwh-desktop.uk.level5networks.com \
    --to=bhutchings@solarflare.com \
    --cc=Kevin.Curtis@farsite.com \
    --cc=dermot.smith@farsite.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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