Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 1/3] ath9k: Fix build error on ARM
Date: Wed, 5 Feb 2014 11:50:35 +0000	[thread overview]
Message-ID: <20140205115035.GO26684@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1391531796.2538.21.camel@joe-AO722>

On Tue, Feb 04, 2014 at 08:36:36AM -0800, Joe Perches wrote:
> On Tue, 2014-02-04 at 08:03 +0100, Holger Schurig wrote:
> > Joe, look in linux/arch/arm/include/asm/delay.h. The macro udelay
> > cannot handle large values because of lost-of-precision.
> > 
> > IMHO udelay on ARM is broken, because it also cannot work with fast
> > ARM processors (where bogomips >= 3355, which is in sight now). It's
> > just not broken enought that someone did something against it ...   so
> > the current kludge is good enought.
> 
> Maybe something like this would be better?

No, the point of __bad_udelay() is that people doing stupidly large
udelay()s result in build errors, rather than having to run the kernel
and trip over a non-existent debugging message beacuse they haven't
built the kernel with DEBUG defined.

NAK.

-- 
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up.  Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".

  parent reply	other threads:[~2014-02-05 11:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04  3:07 [ath9k-devel] [PATCH 0/3] ath9k patches Sujith Manoharan
2014-02-04  3:07 ` [ath9k-devel] [PATCH 1/3] ath9k: Fix build error on ARM Sujith Manoharan
2014-02-04  3:34   ` Joe Perches
2014-02-04  3:40     ` Sujith Manoharan
2014-02-04  7:03       ` Holger Schurig
2014-02-04 12:59         ` [ath9k-devel] [PATCH] checkpatch: Add test for long udelay Joe Perches
2014-02-04 16:36         ` [ath9k-devel] [PATCH 1/3] ath9k: Fix build error on ARM Joe Perches
2014-02-04 18:40           ` Arnd Bergmann
2014-02-04 19:43             ` Joe Perches
2014-02-05 11:50           ` Russell King - ARM Linux [this message]
2014-02-05 12:32             ` Joe Perches
2014-02-05 12:41               ` Russell King - ARM Linux
2014-02-05 13:04                 ` Joe Perches
2014-02-05 13:39                   ` Russell King - ARM Linux
2014-02-05 14:03                     ` Joe Perches
2014-02-05 14:21                       ` Russell King - ARM Linux
2014-02-05 15:05                         ` Joe Perches
2014-02-04  3:07 ` [ath9k-devel] [PATCH 2/3] ath9k: Do not support PowerSave by default Sujith Manoharan
2014-02-04  3:07 ` [ath9k-devel] [PATCH 3/3] ath9k: Fix TX power calculation Sujith Manoharan

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=20140205115035.GO26684@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=ath9k-devel@lists.ath9k.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