From: Prarit Bhargava <prarit@sgi.com>
To: linux-raid@vger.kernel.org, linux-ia64@vger.kernel.org
Cc: Prarit Bhargava <prarit@sgi.com>
Subject: [PATCH 0/2] Fix RAID5 + IA64 compile
Date: Fri, 28 Jul 2006 09:52:03 -0400 [thread overview]
Message-ID: <20060728135203.29357.64980.sendpatchset@prarit.boston.redhat.com> (raw)
Patchset to fix RAID5 on ia64. Removes dead CONFIG options and
introduces a new CONFIG option.
Patch is against 2.6.17 + 2.6.18-rc2-git5
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
next reply other threads:[~2006-07-28 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 13:52 Prarit Bhargava [this message]
2006-07-28 13:52 ` [PATCH 1/2] Fix RAID5 components Prarit Bhargava
2006-07-28 13:52 ` [PATCH 2/2] Fix IA64 components Prarit Bhargava
[not found] <20060728140145.9149.43458.sendpatchset@prarit.boston.redhat.com>
[not found] ` <yq01ws29li9.fsf@jaguar.mkp.net>
2006-07-31 13:12 ` [PATCH 0/2] Fix RAID5 + IA64 compile Prarit Bhargava
2006-07-31 13:13 ` Jes Sorensen
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=20060728135203.29357.64980.sendpatchset@prarit.boston.redhat.com \
--to=prarit@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--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).