public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: linux-kernel@vger.kernel.org
Cc: Skip Ford <skip.ford@verizon.net>
Subject: Re: Alpha update for 2.5.3
Date: Fri, 8 Feb 2002 10:33:05 +0100	[thread overview]
Message-ID: <20020208103305.M4942@suse.de> (raw)
In-Reply-To: <20020208015826.JIFG11848.out009.verizon.net@pool-141-150-235-204.delv.east.verizon.net> <Pine.LNX.4.10.10202071952340.15165-100000@master.linux-ide.org> <20020208040837.MDKA24823.out016.verizon.net@pool-141-150-235-204.delv.east.verizon.net>
In-Reply-To: <20020208040837.MDKA24823.out016.verizon.net@pool-141-150-235-204.delv.east.verizon.net>

On Thu, Feb 07 2002, Skip Ford wrote:
> Andre Hedrick wrote:
> > 
> > That code path will go away!
> > That is a diagnostic path only.
> 
> Sorry Jeff, and others, if that's the wrong patch.  It fixed the compile
> error for ide-dma so I used it.  I still haven't been able to test it
> due to link errors with bus_to_virt.

The patch is correct, I'm the one to blame for forgetting to push that.
And as I stated in my original mail, in the future it will be gone.
However, it still needs to compile right now :-)

> So if Andre is saying don't use it, then don't.  My apologies.

No need to apologise, the patch does the right thing.

-- 
Jens Axboe


      reply	other threads:[~2002-02-08  9:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020207211329.A861@jurassic.park.msu.ru>
2002-02-08  0:59 ` Alpha update for 2.5.3 Richard Henderson
2002-02-08  1:20   ` Jeff Garzik
2002-02-08  1:56     ` Skip Ford
2002-02-08  3:53       ` Andre Hedrick
2002-02-08  4:06         ` Skip Ford
2002-02-08  9:33           ` Jens Axboe [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=20020208103305.M4942@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skip.ford@verizon.net \
    /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