From: Doug Warzecha <Douglas_Warzecha@dell.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] char: Add Dell Systems Management Base driver
Date: Tue, 12 Jul 2005 19:57:16 -0500 [thread overview]
Message-ID: <20050713005716.GA15298@sysman-doug.us.dell.com> (raw)
In-Reply-To: <20050706160737.GC13115@kroah.com>
On Wed, Jul 06, 2005 at 11:07:37AM -0500, Greg KH wrote:
> On Wed, Jul 06, 2005 at 10:57:35AM -0500, Doug Warzecha wrote:
> > On Tue, Jul 05, 2005 at 11:17:03PM -0500, Greg KH wrote:
> > >
> > > I'm sure I commented on this driver already, yet, I never got a
> response
> > > and the code is not changed. Is there some reason for this?
> That's a
> > > sure way to prevent your patch from ever being applied...
> >
> > This is the first comment on the release function. The code has been
> > changing in response to comments from you and others. We'll continue
> > to make changes as needed.
>
> You never responded to those questions though, so determining if the
> code was changed is difficult. And I still see you using ioctls, which,
> if I remember, was what I asked about.
>
The dcdbas driver has been shipping outside of the kernel tree for some time now in support of the systems listed in the source and is expected to support the listed systems for some time to come. The driver has always used ioctls for Dell systems management software to communicate with it. The systems that are supported by the driver are older Dell PowerEdge systems which contain Dell proprietary hardware systems management interfaces. The latest shipping PowerEdge systems support the standard IPMI hardware systems management interface which can be accessed by the in-kernel standard IPMI driver (which uses ioctls). Future PowerEdge systems are expected to support the IPMI systems management interface as well.
Even though the dcdbas driver is not expected to be needed for future PowerEdge systems, we would like to make it easier for Dell customers to run Dell systems management software with the latest kernel on the systems supported by the dcdbas driver by making the driver available in the kernel tree. We would like to do that without impacting the existing Dell systems management software for the older systems so that we can focus our resources on the newer systems.
Is it an absolute "must" that this driver not use ioctls?
Doug
next prev parent reply other threads:[~2005-07-13 0:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 0:13 Doug Warzecha
2005-07-06 0:53 ` Chris Wedgwood
2005-07-12 23:17 ` Doug Warzecha
2005-07-14 21:04 ` Pavel Machek
2005-07-17 3:24 ` Chris Wedgwood
2005-07-06 1:02 ` randy_dunlap
2005-07-06 4:17 ` Greg KH
2005-07-06 15:57 ` Doug Warzecha
2005-07-06 16:07 ` Greg KH
2005-07-06 23:41 ` Doug Warzecha
2005-07-06 23:40 ` Greg KH
2005-07-13 0:57 ` Doug Warzecha [this message]
2005-07-13 20:19 ` Greg KH
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=20050713005716.GA15298@sysman-doug.us.dell.com \
--to=douglas_warzecha@dell.com \
--cc=greg@kroah.com \
--cc=linux-kernel@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®