All of lore.kernel.org
 help / color / mirror / Atom feed
From: "'hch@infradead.org'" <hch@infradead.org>
To: "Mukker, Atul" <Atulm@lsil.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org,
	"'torvalds@osdl.org'" <torvalds@osdl.org>,
	"'marcelo.tosatti@cyclades.com'" <marcelo.tosatti@cyclades.com>,
	Matt_Domsch@dell.com
Subject: Re: ANNOUNCE: megaraid driver version 2.10.1
Date: Sun, 11 Jan 2004 14:06:40 +0000	[thread overview]
Message-ID: <20040111140640.A21952@infradead.org> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57033BC2AA@exa-atlanta.se.lsil.com>; from Atulm@lsil.com on Fri, Jan 09, 2004 at 06:54:09PM -0500

On Fri, Jan 09, 2004 at 06:54:09PM -0500, Mukker, Atul wrote:
> All,
> 
> The megaraid driver version 2.10.1 is released and can be downloaded from
> ftp://ftp.lsil.com/pub/linux-megaraid/drivers/version-2.10.1/
> 
> Following other components are also available at this location:
> i.	Patches for Red Hat and SuSE stock kernels

Can't find patches for mainline anywhere.  Also it's usually a good
idea to send the _patches_ to lkml for review.

I've diffed the driver against the 2.4 megaraid2 driver and it looks
mostly sane, the 2.6 version OTOH copletly backs out the changes that
went into the driver from outside LSI.  Please try to port the changes
you made to the driver in 2.6.1.


  reply	other threads:[~2004-01-11 14:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09 23:54 ANNOUNCE: megaraid driver version 2.10.1 Mukker, Atul
2004-01-11 14:06 ` 'hch@infradead.org' [this message]
2004-01-10 13:52 Xose Vazquez Perez
2004-01-13 21:39 Mukker, Atul
2004-01-14  9:22 ` 'hch@infradead.org'
2004-01-30 15:03 Mukker, Atul
2004-01-30 15:40 ` 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=20040111140640.A21952@infradead.org \
    --to=hch@infradead.org \
    --cc=Atulm@lsil.com \
    --cc=Matt_Domsch@dell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=torvalds@osdl.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.