From: Jeff Garzik <jgarzik@pobox.com>
To: Lukasz Kosewski <lkosewsk@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2.6.15-rc7-git3 1/3] sata_promise: add correct read/write of hotplug registers for SATAII devices
Date: Sat, 28 Jan 2006 12:39:48 -0500 [thread overview]
Message-ID: <43DBAC64.1070902@pobox.com> (raw)
In-Reply-To: <355e5e5e0512291523h508fe0c8j459a9377d52d5529@mail.gmail.com>
Lukasz Kosewski wrote:
> This patch adds support for correctly masking out and knowing about
> hotplug events on Promise SATAII150 Tx4/Tx2 Plus controllers.
>
> Signed-off-by: Luke Kosewski <lkosewsk@gmail.com>
applied
prev parent reply other threads:[~2006-01-28 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-29 23:23 [PATCH 2.6.15-rc7-git3 1/3] sata_promise: add correct read/write of hotplug registers for SATAII devices Lukasz Kosewski
2005-12-30 15:09 ` Alan Cox
2006-01-28 17:39 ` Jeff Garzik [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=43DBAC64.1070902@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkosewsk@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;
as well as URLs for NNTP newsgroup(s).