From: David Miller <davem@davemloft.net>
To: Eric.Moore@lsil.com
Cc: tcallawa@redhat.com, linux-scsi@vger.kernel.org,
sparclinux@vger.kernel.org, James.Bottomley@SteelEye.com
Subject: Re: [PATCH] Build mptspi.c on architectures where CONFIG_PM is unset
Date: Wed, 14 Jun 2006 16:47:39 -0700 (PDT) [thread overview]
Message-ID: <20060614.164739.50340788.davem@davemloft.net> (raw)
In-Reply-To: <664A4EBB07F29743873A87CF62C26D70199769@NAMAIL4.ad.lsil.com>
From: "Moore, Eric" <Eric.Moore@lsil.com>
Date: Wed, 14 Jun 2006 17:16:27 -0600
> ACK, James pls apply to your scsi-misc tree.
Don't bother, I already pushed this fix into Linus's tree. :-)
next prev parent reply other threads:[~2006-06-14 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 23:16 [PATCH] Build mptspi.c on architectures where CONFIG_PM is unset Moore, Eric
2006-06-14 23:47 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-03 14:36 Tom 'spot' Callaway
2006-06-10 0:00 ` David Miller
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=20060614.164739.50340788.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Eric.Moore@lsil.com \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=tcallawa@redhat.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