All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IPMI driver updates for 2.4
Date: Tue, 31 Aug 2004 19:38:15 -0500	[thread overview]
Message-ID: <413519F7.3000004@acm.org> (raw)
In-Reply-To: <20040831111621.GE4615@logos.cnet>

There actually aren't any bug fixes.  These are all new feature 
additions.  It is a big driver revamp, but it has been around for a while

I guess it is not critical now, but it would be nicer for the users of 
the driver.

-Corey

Marcelo Tosatti wrote:

>Hi Corey, 
>
>You wrote a nice changelog entry - thanks for that.
>
>I'm not sure if we should apply all of this in v2.4. It looks like a
>big driver revamp to me. 
>
>Is is all this critical for being merged in v2.4.x now? 
>
>Would it be very painful/unwanted to maintain only the bugfixes 
>and not only new features? What you think about that?
>
>On Sun, Aug 29, 2004 at 10:39:38PM -0500, Corey Minyard wrote:
>  
>
>>Marcelo Tosatti wrote:
>>
>>    
>>
>>>Corey,
>>>
>>>Care to write a detailed changelog so we can apply this?
>>>
>>>Thanks
>>>
>>>
>>>
>>>      
>>>
>>I'm sorry this took so long, I have been dealing with disasters at work.
>>
>>Ok, a detailed changelog:
>>
>>* Add a new "system interface" driver that supports all the standard
>> IPMI system interfaces (SMIC, BT, and KCS, see the IPMI spec for
>> more details if you care).  This driver will auto-detect the interface
>> type and parameters via SMBIOS or ACPI tables.
>>* Deprecate the old KCS-only interface.
>>* Support non-contiguous registers for system interfaces.
>>* Add support for IPMI LAN bridging so messages can be received
>> from and sent to system software connected to a LAN interface.
>>* Add support for powering off the system on a halt via the IPMI
>> interface.
>>* Add support for storing panic logs in the IPMI event log.
>>* Allow control of message parameters (resends, timeouts)
>>
>>I've also re-attached the patch.
>>
>>Thanks,
>>    
>>


  reply	other threads:[~2004-09-01  0:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <411EB8F1.5040209@acm.org>
     [not found] ` <20040823132820.GB2157@logos.cnet>
     [not found]   ` <4132A17A.8060607@acm.org>
2004-08-31 11:16     ` IPMI driver updates for 2.4 Marcelo Tosatti
2004-09-01  0:38       ` Corey Minyard [this message]
2004-09-11 17:44         ` Marcelo Tosatti
2004-09-13 13:32           ` Corey Minyard
2004-09-13 18:18             ` Marcelo Tosatti

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=413519F7.3000004@acm.org \
    --to=minyard@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.