linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: "Labun, Marcin" <Marcin.Labun@intel.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
	"Williams, Dan J" <dan.j.williams@intel.com>,
	"Ciechanowski, Ed" <ed.ciechanowski@intel.com>,
	"Neubauer, Wojciech" <Wojciech.Neubauer@intel.com>
Subject: Re: [PATCH 00/14] OROM/EFI support for Intel SAS and AHCI controllers in IMSM
Date: Thu, 10 Mar 2011 11:55:06 +1100	[thread overview]
Message-ID: <20110310115506.5cf6616d@notabene.brown> (raw)
In-Reply-To: <905EDD02F158D948B186911EB64DB3D17A8AEC88@irsmsx503.ger.corp.intel.com>

On Tue, 8 Mar 2011 15:20:20 +0000 "Labun, Marcin" <Marcin.Labun@intel.com>
wrote:

> >From 8851572a406e938f50466a98405b10529048e766 Mon Sep 17 00:00:00 2001
> From: Marcin Labun <marcin.labun@intel.com>
> Date: Tue, 8 Mar 2011 15:24:09 +0100
> Subject: [PATCH 00/14] OROM/EFI support for Intel SAS and AHCI controllers in IMSM
> 
> IMSM metadata supports retrieving RAID capabilities for:
> - Intel SAS controller with Legacy OROM
> - Intel SAS controller with EFI
> - Intel AHCI controller with Legacy OROM
> - AHCI controller with EFI
> IMSM Metadata handlers constrain RAID configurations to those supported EFI/OROM for Intel AHCI or SAS controller.

I have applied all of these - though with some little fixes so that
it compiled correctly after each commit.

I admit that I don't understand much of it so I didn't review it closely.
Hopefully internal review (e.g. from Dan) is sufficient.

Thanks,
NeilBrown


> 
> 
> Marcin Labun (11):
>   probe_roms: allow to probe expansion ROMs using vendor and device id.
>   Platform-intel: support for OROM SAS and AHCI controller
>   imsm: remove unused parameters in function attach_hba_to_super
>   imsm: detail_platform_imsm displays AHCI and SAS controller
>     information
>   imsm: do not publish OROM/EFI unsupported arrays
>   imsm: print-out error message when volume validation fails
>   imsm: add maximum number of disk validation in RAID array
>   imsm: verify that component disks are attached to the same type of
>     HBA
>   imsm: move code for retrieving HBA to a function
>   imsm: introduce SAS controller support in imsm metadata handler
>   platform_intel: support for OROM OEM capabilities
> 
> Przemyslaw Czarnowski (3):
>   update of imsm_orom structure
>   Some guid manipulation utilities has been added.
>   read platform capabilities from EFI
> 
>  platform-intel.c |  221 ++++++++++++++++++++++++++++++-----
>  platform-intel.h |   39 ++++++-
>  probe_roms.c     |   29 ++++-
>  probe_roms.h     |    2 +-
>  super-intel.c    |  339 +++++++++++++++++++++++++++++++++++++-----------------
>  5 files changed, 488 insertions(+), 142 deletions(-)


      reply	other threads:[~2011-03-10  0:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 15:20 [PATCH 00/14] OROM/EFI support for Intel SAS and AHCI controllers in IMSM Labun, Marcin
2011-03-10  0:55 ` NeilBrown [this message]

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=20110310115506.5cf6616d@notabene.brown \
    --to=neilb@suse.de \
    --cc=Marcin.Labun@intel.com \
    --cc=Wojciech.Neubauer@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=ed.ciechanowski@intel.com \
    --cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).