From: Tore Anderson <tore@linpro.no>
To: brking@us.ibm.com
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [patch 15/15] ipr: Support attaching SATA devices
Date: Tue, 07 Feb 2006 15:51:20 +0100 [thread overview]
Message-ID: <1139323880.20401.73.camel@echo.e.linpro.no> (raw)
In-Reply-To: <200602061542.k16FgdNU025771@d03av04.boulder.ibm.com>
* brking@us.ibm.com
> -#define IPR_DRIVER_VERSION "2.1.1"
> -#define IPR_DRIVER_DATE "(November 15, 2005)"
> +#define IPR_DRIVER_VERSION "2.2.0"
> +#define IPR_DRIVER_DATE "(February 6, 2005)"
^^^^ You mean 2006, yes?
Regards
--
Tore Anderson
next prev parent reply other threads:[~2006-02-07 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 15:42 [patch 15/15] ipr: Support attaching SATA devices brking
2006-02-07 14:51 ` Tore Anderson [this message]
2006-02-07 15:02 ` Brian King
-- strict thread matches above, loose matches on Subject: below --
2006-03-17 23:05 [PATCH " Brian King
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=1139323880.20401.73.camel@echo.e.linpro.no \
--to=tore@linpro.no \
--cc=brking@us.ibm.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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).