From: Yiannis Mavroukakis <jander@darthvader.us>
To: linux-scsi@vger.kernel.org
Subject: Re: legacy megaraid driver bug in mm-series
Date: Thu, 08 Sep 2005 08:56:25 +0100 [thread overview]
Message-ID: <431FEEA9.60407@darthvader.us> (raw)
In-Reply-To: <20050907133355.54f3dd2d.akpm@osdl.org>
Andrew Morton wrote:
>"Ju, Seokmann" <sju@lsil.com> wrote:
>
>
>>Hi Andrew,
>>On Wednesday, September 07, 2005 5:53 AM, Andrew Morton forwarded:
>>
>>
>>>2.6.11-mm1: works
>>>2.6.11-mm4: works
>>>2.6.12-rc5-mm1: will not compile
>>>2.6.12-rc6-mm1: works
>>>2.6.12-mm1: will not compile megaraid driver
>>>2.6.12-mm2: broken
>>>2.6.13-mm1: broken
>>>
>>>2.6.12: works
>>>2.6.13: works
>>>
>>>
>>Is there any precedence rule on the kernels?.
>>
>>
>>
>
>It's a bit weird, but the above are in chronological order.
>
>Time order:
>
> 2.6.12
> 2.6.13-rc1
> 2.6.13-rc2
> 2.6.13
> 2.6.14-rc1
>
>etc. And -mm kernels are just the current Linus kernel with -mmX appended.
>
>
>
>>I wonder which kernel is latest in between 2.6.12 and 2.6.12-mmx.
>>
>>
>
>2.6.12-mmX
>
>
>
>>I assume 2.6.12-mmx is later than 2.6.12.
>>
>>
>
>Correct.
>
>
>
2.6.13-mm1 doesn't work on my megaraid controller.
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
next prev parent reply other threads:[~2005-09-08 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 17:00 legacy megaraid driver bug in mm-series Ju, Seokmann
2005-09-07 20:33 ` Andrew Morton
2005-09-08 7:56 ` Yiannis Mavroukakis [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-08 19:26 Ju, Seokmann
2005-09-08 19:00 Ju, Seokmann
2005-09-06 1:05 Jack Byer
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=431FEEA9.60407@darthvader.us \
--to=jander@darthvader.us \
--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 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.