All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Dave Jones <davej@codemonkey.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PATCH: IPMI driver
Date: Thu, 09 Jan 2003 13:16:29 -0600	[thread overview]
Message-ID: <3E1DCA8D.4040005@acm.org> (raw)
In-Reply-To: 1042135971.27796.44.camel@irongate.swansea.linux.org.uk

Alan Cox wrote:

>On Thu, 2003-01-09 at 17:22, Dave Jones wrote:
>  
>
>>On Thu, Jan 09, 2003 at 06:06:34PM +0000, Alan Cox wrote:
>>
>> > Arghhh I was told Linus accepted it, and my tree indexer found "IPMI" so
>> > decided it was present too. (Only the i2c definitions apparently).
>>
>>Shouldn't cause any problems in 2.4 anyways should it ?
>>After all, its 'just another driver'.
>>
>> > Oh well, it should be in 2.5
>>
>>Added to the queue of bits from the 2.4 changesets list that I'm
>>intending to push to Linus soon.
>>    
>>
>
>Pull the 2.5 port from openipmi.sourceforge.net  saves you doing the port
>yourself. 
>
Definately pull the 2.5 port from there, as there are some differences 
between the 2.4 and 2.5 versions.

-Corey



  reply	other threads:[~2003-01-09 19:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200301090332.h093WML05981@hera.kernel.org>
2003-01-09 16:44 ` [PATCH] PATCH: IPMI driver Dave Jones
2003-01-09 18:06   ` Alan Cox
2003-01-09 17:22     ` Dave Jones
2003-01-09 18:12       ` Alan Cox
2003-01-09 19:16         ` Corey Minyard [this message]
2003-01-09 19:20           ` Dave Jones
2003-01-09 19:37             ` Corey Minyard
2003-01-09 20:17             ` Alan Cox
2003-01-09 19:37               ` Dave Jones
2003-01-09 20:42               ` Jeff Garzik

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=3E1DCA8D.4040005@acm.org \
    --to=minyard@acm.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davej@codemonkey.org.uk \
    --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 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.