public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: HighPoint Linux Team <linux@highpoint-tech.com>
Cc: linux-scsi@vger.kernel.org, jejb@steeleye.com,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] hptiop: backout ioctl mess
Date: Thu, 03 Aug 2006 00:55:37 +0200	[thread overview]
Message-ID: <1154559337.2861.2.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <08ce01c6b44c$82b8ef70$1200a8c0@gmm>

On Mon, 2006-07-31 at 10:53 +0800, HighPoint Linux Team wrote:
> Christoph Hellwig wrote:
> > The hptiop just got merged with a horrible amount of really bad ioctl
> > code that is against the standards for new scsi drivers.  This patch
> > backs it out (and fixes a small bug where scsi_add_host is called to
> > early).  We can re-add proper APIs once we agree on them.
> 
> What is the standard implemetation of private ioctls for scsi drivers?
> Thanks.

Hi,

the real answer is: try really hard to use generic ioctls for your
functionality. What exactly do you need private ioctls for?
It's quite possible that there is a generic way to do the same thing
already, or something that can easily be extended to do what you need...

Greetings,
   Arjan van de Ven
-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com


  parent reply	other threads:[~2006-08-03  2:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-30 17:13 [PATCH] hptiop: backout ioctl mess Christoph Hellwig
2006-07-31  2:53 ` HighPoint Linux Team
2006-07-31  3:19   ` Douglas Gilbert
2006-08-02 22:55   ` Arjan van de Ven [this message]
2006-08-03  3:12     ` HighPoint Linux Team
2006-08-03  3:29     ` Douglas Gilbert
2006-08-03 11:02       ` Arjan van de Ven
2006-08-06 18:18 ` James Bottomley
2006-09-12  5:40   ` HighPoint Linux Team

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=1154559337.2861.2.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=hch@lst.de \
    --cc=jejb@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@highpoint-tech.com \
    /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