Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: adam radford <aradford@gmail.com>
Cc: Neela Syam Kolli <megaraidlinux@lsi.com>,
	Buford Peek <BPeek@lancope.com>,
	666108@bugs.debian.org, Gator_Yin@dell.com,
	linux-scsi@vger.kernel.org,
	Priyantha Bleeker <priyantha.bleeker@gmail.com>,
	Edward Konetzko <konetzed@gmail.com>
Subject: Re: megaraid_sas: which patches are needed for 2.6.32.y?
Date: Mon, 29 Oct 2012 04:50:49 -0700	[thread overview]
Message-ID: <20121029115049.GA28465@elie.Belkin> (raw)
In-Reply-To: <CAHtARFHafR+hrB4u=wDUSE3-J2uXOQCFHW3wRSQMiebowu-9iA@mail.gmail.com>

Hi,

In June, adam radford wrote:
> On Thu, Jun 28, 2012 at 1:27 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:

>> If someone makes a backport of the patches marked [3] as well, would
>> you be able to look over or test the combination?  That would be much
>> appreciated.  If that's not possible, your advice would still be
>> welcome but we will need to use a more minimal set of changes.
>
> Yes, I will be able to look over and/or test the combination.  If you
> apply all patches then diff vs. the scsi-misc tip, you should only see
> kernel 2.6.32.y specific changes.

Sorry for the long delay.

I've made a backport with all relevant patches I could find from the
3.0.y tree and put the patches and a built package at

  http://alioth.debian.org/~jrnieder-guest/temp/driver-test/

Patches are against 2.6.32.y.  The most notable missing patch is the
BKL conversion --- for Debian squeeze it seems safest to just keep
using the BKL.  I'd be happy for any thoughts you have.

Thanks,
Jonathan

  reply	other threads:[~2012-10-29 11:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <FB09F9AF3FE25444B277AA82BB35EE175F0260C0@LCHQEX03.lancope.local>
     [not found] ` <20120328192623.GB8982@burratino>
     [not found]   ` <FB09F9AF3FE25444B277AA82BB35EE175F02612C@LCHQEX03.lancope.local>
     [not found]     ` <FB09F9AF3FE25444B277AA82BB35EE175F028482@LCHQEX03.lancope.local>
     [not found]       ` <20120329165806.GC3147@burratino>
     [not found]         ` <FB09F9AF3FE25444B277AA82BB35EE175F0284E2@LCHQEX03.lancope.local>
     [not found]           ` <20120329194751.GG3147@burratino>
     [not found]             ` <20120609164753.GA18761@burratino>
2012-06-24 15:13               ` megaraid_sas: which patches are needed for 2.6.32.y? Jonathan Nieder
2012-06-28 19:19                 ` adam radford
2012-06-28 20:27                   ` Jonathan Nieder
2012-06-29 16:25                     ` adam radford
2012-10-29 11:50                       ` Jonathan Nieder [this message]
2012-11-25  9:47                         ` Jonathan Nieder
     [not found] <CAD2iGhWrruwSWtNo9pVH1Aufimq1W2G3VQKEHaWnmoXjnNk4cQ@mail.gmail.com>
     [not found] ` <20121203144310.GA1357@elie.Belkin>
     [not found]   ` <CAD2iGhWegHsB+1P9unXn6sfveSQGFyahH9qKh4oHtXpxDSz1EA@mail.gmail.com>
2012-12-04  6:27     ` Jonathan Nieder

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=20121029115049.GA28465@elie.Belkin \
    --to=jrnieder@gmail.com \
    --cc=666108@bugs.debian.org \
    --cc=BPeek@lancope.com \
    --cc=Gator_Yin@dell.com \
    --cc=aradford@gmail.com \
    --cc=konetzed@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=megaraidlinux@lsi.com \
    --cc=priyantha.bleeker@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox