From: Jamie Lenehan <lenehan@twibble.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] dc395x fix memory mapping (was Re: dc395x: can't write to tape)
Date: Wed, 23 Feb 2005 21:16:18 +1100 [thread overview]
Message-ID: <20050223101615.GA5930@twibble.org> (raw)
In-Reply-To: <Pine.LNX.4.60.0502212258460.5642@poirot.grange>
On Mon, Feb 21, 2005 at 11:01:27PM +0100, Guennadi Liakhovetski wrote:
> On Sun, 6 Feb 2005, Guennadi Liakhovetski wrote:
>
> > Two weeks since I posted this patch - ping...
>
> ...and another two weeks since you, Jamie, replied to me privately. Just
> wanted to say, it would be good to get this bug fixed for the post-2.6.11
> SCSI patch.
Yep.
I've been rather busy and have not had any time to look at this. The patch
looks good and I've had no issues testing it now with highmem enabled on my
4G DAT drive.
I'll submit the patch in a minute.
Thanks.
Jamie.
--
Jamie Lenehan <lenehan@twibble.org>
prev parent reply other threads:[~2005-02-23 10:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 10:18 dc395x: can't write to tape Andrew Schulman
2005-01-06 21:48 ` Guennadi Liakhovetski
2005-01-07 10:52 ` Andrew Schulman
2005-01-07 20:13 ` Guennadi Liakhovetski
2005-01-08 21:42 ` Guennadi Liakhovetski
2005-01-11 15:19 ` Andrew Schulman
2005-01-11 22:16 ` Guennadi Liakhovetski
2005-01-12 8:58 ` Andrew Schulman
2005-01-09 5:33 ` Jamie Lenehan
2005-01-09 11:42 ` Guennadi Liakhovetski
2005-01-09 12:51 ` Jamie Lenehan
2005-01-22 23:20 ` Guennadi Liakhovetski
2005-01-27 1:13 ` Andrew Schulman
2005-01-27 20:45 ` Guennadi Liakhovetski
2005-02-06 22:11 ` [PATCH] dc395x fix memory mapping (was Re: dc395x: can't write to tape) Guennadi Liakhovetski
2005-02-21 22:01 ` Guennadi Liakhovetski
2005-02-23 10:16 ` Jamie Lenehan [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=20050223101615.GA5930@twibble.org \
--to=lenehan@twibble.org \
--cc=g.liakhovetski@gmx.de \
--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