From: "HighPoint Linux Team" <linux@highpoint-tech.com>
To: Christoph Hellwig <hch@lst.de>
Cc: jejb@SteelEye.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] hptiop: backout ioctl mess
Date: Tue, 12 Sep 2006 13:40:33 +0800 [thread overview]
Message-ID: <016101c6d62d$fc6e3070$1200a8c0@GMM> (raw)
In-Reply-To: 1154888332.3683.231.camel@mulgrave.il.steeleye.com
James Bottomley wrote:
> On Sun, 2006-07-30 at 19:13 +0200, 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.
>
> I'm assuming the model you want to use is megaraid_sas, which only has a
> couple of defined ioctls?
>
> > Please send this to Linus for 2.6.19 so that the ioctls don't make it
> > into a release.
>
> OK, provided you take the lead in sorting out the ioctl infrastructure
> for this driver ...
>
> James
>
Is there a suggested solution now? We just want RAID management
functions to work on this driver. Is it ok to use register_chrdev()
for the management interface like megaraid_sas?
HighPoint Linux Team
prev parent reply other threads:[~2006-09-12 5:40 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
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 [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='016101c6d62d$fc6e3070$1200a8c0@GMM' \
--to=linux@highpoint-tech.com \
--cc=hch@lst.de \
--cc=jejb@SteelEye.com \
--cc=linux-scsi@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