public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: GOTO Masanori <gotom@debian.or.jp>
To: Andi Kleen <ak@muc.de>
Cc: GOTO Masanori <gotom@debian.or.jp>,
	linux-scsi@vger.kernel.org, yokota@netlab.is.tsukuba.ac.jp
Subject: Re: [PATCH] Mark Workbit NinjaSCSI driver non 64bit
Date: Mon, 05 Jan 2004 23:01:42 +0900	[thread overview]
Message-ID: <81n092qyt5.wl@omega.webmasters.gr.jp> (raw)
In-Reply-To: <20040103232718.GA6881@averell>

Hi,

At Sun, 4 Jan 2004 00:27:19 +0100,
Andi Kleen wrote:
> On Sun, Jan 04, 2004 at 03:08:59AM +0900, GOTO Masanori wrote:
> > At Thu, 1 Jan 2004 22:58:35 +0100,
> > Andi Kleen wrote:
> > > Judging from the warnings it spews out on a 64bit compilation on AMD64
> > > it is not 64bit clean.  Mark it as such in Kconfig.
> > > 
> > > Better would be of course to fix it.
> > 
> > Thanks for your report.  I compiled and exactly I saw some warnings on
> > amd64 machine.  I checked all warnings, and these warnings are
> > trivial, they can be easily fixed.  I attached the patch to fix
> > warnings.  Nsp32 is PCI device driver, so it should also work on amd64
> > architecture.
> 
> Thanks.
> 
> Did you test if it works on the AMD64 machine? Sometimes there are 64bit
> issues that don't show as warnings.

I can login almost all architecture machine, but unfortunately I have
no 64bit with PCI machine at home at present.  However, possibly I
have an opportunity to touch amd64 machine, so I will try to test
nsp32 on amd64.

BTW, at least I have taken care about ILP32 vs LP64, so even if it
does not work on amd64, it's not hard to make ok, I believe.

Regards,
-- gotom

      reply	other threads:[~2004-01-05 14:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-01 21:58 [PATCH] Mark Workbit NinjaSCSI driver non 64bit Andi Kleen
2004-01-03 18:08 ` GOTO Masanori
2004-01-03 23:27   ` Andi Kleen
2004-01-05 14:01     ` GOTO Masanori [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=81n092qyt5.wl@omega.webmasters.gr.jp \
    --to=gotom@debian.or.jp \
    --cc=ak@muc.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=yokota@netlab.is.tsukuba.ac.jp \
    /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