public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Andreas Schwab <schwab@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] block highmem zero-bounce #17
Date: Fri, 19 Oct 2001 15:59:42 +0200	[thread overview]
Message-ID: <20011019155942.C7221@suse.de> (raw)
In-Reply-To: <20011018144047.E4825@suse.de> <jen12n4w1v.fsf@sykes.suse.de> <20011019151023.D5509@suse.de> <jed73j4tqo.fsf@sykes.suse.de>
In-Reply-To: <jed73j4tqo.fsf@sykes.suse.de>

On Fri, Oct 19 2001, Andreas Schwab wrote:
> |> On Fri, Oct 19 2001, Andreas Schwab wrote:
> |> > Jens Axboe <axboe@suse.de> writes:
> |> > 
> |> > |> Patch is considered solid. Find it here:
> |> > |> 
> |> > |> *.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.13-pre4/block-highmem-all-17.bz2
> |> > 
> |> > Your patch still makes bad use of struct scatterlist which is architecture
> |> > dependent.  Either fix the definitions in asm-*/scatterlist.h or go back
> |> > using a private struct.  Why did you switch to struct scatterlist in the
> |> > first place??
> |> 
> |> What are you talking about? Please expand. struct scatterlist has very
> |> intentionally been changed to its current look, and if an arch is not
> |> uptodate please let me know.
> 
> Currently ia64 does not build due to this.

Then the IA64 folks need to catch up. There's nothing new in this, this
is how stuff usually happens. In short, I don't see the problem.

-- 
Jens Axboe


  reply	other threads:[~2001-10-19 13:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-18 12:40 [patch] block highmem zero-bounce #17 Jens Axboe
2001-10-19 13:08 ` Andreas Schwab
2001-10-19 13:10   ` Jens Axboe
2001-10-19 13:58     ` Andreas Schwab
2001-10-19 13:59       ` Jens Axboe [this message]
2001-10-19 13:13   ` Jens Axboe

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=20011019155942.C7221@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwab@suse.de \
    /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