mirror of https://lore.kernel.org/lkml/
 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 005/007] WAN Drivers: Update farsync driver and introduce fsflex driver
Date: Wed, 18 Sep 2013 16:44:52 +0100	[thread overview]
Message-ID: <1379519092.1522.27.camel@bwh-desktop.uk.level5networks.com> (raw)
In-Reply-To: <E603DC592C92B54A89CEF6B0919A0B1CAAAA787DA4@SOLO.hq.farsitecommunications.com>

On Wed, 2013-09-18 at 11:12 +0100, Kevin Curtis wrote:
> Farsite Communications FarSync driver update
> 
> Patch 5 of 7
> Note that this patch must be applied with patch 4 (farsync_include_patch)
> 
> Update the current farsync driver to support all of the PCI and PCI X
> cards manufactured by Farsite Communications.
> 
> Add a tty interface so that the ports can also be used by the ppp daemon.
> 
> Add support for big endian systems (the FarSite cards have a little endian
> processor on board).
[...]

Should all be separate patches.  This is just doing way too much in one
go.

And there are regressions in here like:

>  static struct pci_driver fst_driver = {
> -        .name          = FST_NAME,
> -        .id_table      = fst_pci_dev_id,
> -        .probe         = fst_add_one,
> -        .remove        = fst_remove_one,
> -        .suspend       = NULL,
> -        .resume        = NULL,
> +name: FST_NAME,
> +id_table : fst_pci_dev_id,
> +probe : fst_add_one,
> +remove : fst_remove_one,
> +suspend : NULL,
> +resume : NULL,
> +};

And the addition of a file in procfs (at the top level, even!) as if
it's still 2001 and sysfs doesn't exist:

> +static int farsync_proc_open(struct inode *inode, struct file *file)
> +{
> +       return single_open(file, fst_proc_info, NULL);
> +}
> +
> +static const struct file_operations farsync_proc_fops = {
> +       .open = farsync_proc_open,
> +       .read = seq_read,
> +       .llseek = seq_lseek,
> +       .release = single_release,
>  };

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:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 10:12 Kevin Curtis
2013-09-18 15:42 ` Joe Perches
2013-09-18 15:44 ` 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=1379519092.1522.27.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

all inboxes | Powered by JetHome®