public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 2.6.11-rc2 1/1] altix: Device driver support for the CX port of SGI's TIO chip
Date: Fri, 11 Feb 2005 14:26:55 +0000	[thread overview]
Message-ID: <20050211142655.GA6113@infradead.org> (raw)
In-Reply-To: <20050211140321.20148.62620.40637@attica.americas.sgi.com>

> -#include "xtalk/xwidgetdev.h"
> +#include <asm/sn/xtalk/xwidgetdev.h>
>  #include <asm/sn/geo.h>
> -#include "xtalk/hubdev.h"
> +#include <asm/sn/xtalk/hubdev.h>

please put moving around headers in a separate patch.

>  DEFINE_PER_CPU(struct pda_s, pda_percpu);
> +EXPORT_PER_CPU_SYMBOL(pda_percpu);

As mentioned the last time you posted it please use a proper accessor.

> +static void tiocx_bus_release(struct device *dev)
> +{
> +}

this is broken.  See the tweleve gazillion times it came up on lkml.
The driver core doesn't warn about the lack of a release function because
it's a nice way to waste time but because there's an actual reason.

> +struct cx_drv {
> +	char *name;
> +	const struct cx_device_id *id_table;
> +	struct device_driver driver;
> +	int (*probe) (struct cx_dev * dev, const struct cx_device_id * id);
> +};

To make it work sanely you also need a ->remove callout.


With the above issues fixed it's fine to be queued up until you submit
an actual user of this interface.

  reply	other threads:[~2005-02-11 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11 14:03 [PATCH 2.6.11-rc2 1/1] altix: Device driver support for the CX port of SGI's TIO chip Bruce Losure
2005-02-11 14:26 ` Christoph Hellwig [this message]
2005-02-11 20:40 ` [PATCH 2.6.11-rc2 1/1] altix: Device driver support for the CX Bruce Losure
2005-02-15 13:27 ` [PATCH 2.6.11-rc2 1/1] altix: Device driver support for the CX port of SGI's TIO chip Christoph Hellwig
2005-02-15 15:45 ` [PATCH 2.6.11-rc2 1/1] altix: Device driver support for the CX Bruce Losure

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=20050211142655.GA6113@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-ia64@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