From: Jens Axboe <axboe@suse.de>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][CFT] IDE TCQ #2
Date: Wed, 10 Apr 2002 12:09:19 +0200 [thread overview]
Message-ID: <20020410100919.GH2485@suse.de> (raw)
In-Reply-To: <20020409124417.GK25984@suse.de> <3CB3FDF7.6010505@evision-ventures.com> <20020410095829.GG2485@suse.de> <3CB40036.7010504@evision-ventures.com>
On Wed, Apr 10 2002, Martin Dalecki wrote:
> Jens Axboe wrote:
> >On Wed, Apr 10 2002, Martin Dalecki wrote:
> >
> >>Jens Axboe wrote:
> >>
> >>>Hi,
> >>>
> >>>Version 2 is ready. Changes since last time:
> >>
> >>Hi,
> >>
> >>OK I have managed to merge this with the 2.5.8-pre2 + ide-29b at home.
> >>However since we have now apparently already a -pre3 I will have
> >>to at least redo the patches against it. If this takes more
> >>then the time needed for a cup of coffe I will have unfortuntely to
> >>do it today afternoon.
> >
> >
> >I'm already running 2.5.8-pre3 (which appears to include ide-29b,
> >right?) + ide-tcq here, so you should probably not waste any effort on
> >that :-)
>
> Well than I will have to basically redo all the
> stuff I did in between... like for example nuking the
> number of parameters to ata_taskfile()... :-(.
Ok, go ahead with the merge then and keep your changes. I'll just diff
#2 -> current and apply that to whatever shows up in the next kernel.
--
Jens Axboe
next prev parent reply other threads:[~2002-04-10 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 12:44 [PATCH][CFT] IDE TCQ #2 Jens Axboe
2002-04-09 12:24 ` Martin Dalecki
2002-04-09 13:41 ` Jens Axboe
2002-04-10 8:55 ` Martin Dalecki
2002-04-10 9:58 ` Jens Axboe
2002-04-10 9:04 ` Martin Dalecki
2002-04-10 10:09 ` Jens Axboe [this message]
2002-04-10 9:12 ` Martin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2002-04-09 15:34 Andries.Brouwer
2002-04-09 15:22 ` Martin Dalecki
2002-04-09 16:38 Andries.Brouwer
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=20020410100919.GH2485@suse.de \
--to=axboe@suse.de \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@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