Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Martin Michlmayr <tbm@cyrius.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-scsi@vger.kernel.org,
	james.bottomley@HansenPartnership.com,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH] scsi: Fix bad use of udelay in atp870u.c
Date: Fri, 17 Oct 2008 07:48:42 +0200	[thread overview]
Message-ID: <20081017054842.GG25834@deprecation.cyrius.com> (raw)
In-Reply-To: <20081016155135.8fc411ae.akpm@linux-foundation.org>

* Andrew Morton <akpm@linux-foundation.org> [2008-10-16 15:51]:
> > +	mdelay(2);
> > +	udelay(48);
> >  	if ((inb(tmport) & 0x80) == 0x00) {	/* bsy ? */
> >  		outw(0, tmport--);
> >  		outb(0, tmport);
> > 
> 
> hum.  The code has been like that for many years - why was the
> error only discovered now.  Is that check in arm new?

I don't think so.  I cannot remember for sure, but I probably ran into
it when we started moving the Debian ARM kernels from a config file
that only selected a limited number of modules to a more generic
config file that enables as much as possible.  I don't think anyone
cares about this one driver in particular, but it's hard to know which
modules users need, so we enable everything we can.

Anyway, we've carried a patch around since December 2007 that disables
this module on ARM because of this compilation error, but I'd like to
get this resolved in the mainline kernel.

> If so, was it present in 2.6.27?
>   If so, does anyone actually use this driver on arm?
>     If so, we'll need this patch in 2.6.27.x as well.

Nah, fixing it for 2.6.28 would be fine.
-- 
Martin Michlmayr
http://www.cyrius.com/

  reply	other threads:[~2008-10-17  5:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16  8:21 [PATCH] scsi: Fix bad use of udelay in atp870u.c Martin Michlmayr
2008-10-16 22:51 ` Andrew Morton
2008-10-17  5:48   ` Martin Michlmayr [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-09-30  7:39 Martin Michlmayr

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=20081017054842.GG25834@deprecation.cyrius.com \
    --to=tbm@cyrius.com \
    --cc=akpm@linux-foundation.org \
    --cc=james.bottomley@HansenPartnership.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --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