All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Leete <tleete@mountain.net>
To: Bill Wendling <wendling@ganymede.isdn.uiuc.edu>
Cc: Andre Hedrick <andre@linux-ide.org>,
	Pozsar Balazs <pozsy@sch.bme.hu>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [IDE] meaningless #ifndef?
Date: Mon, 19 Feb 2001 23:45:19 -0500	[thread overview]
Message-ID: <3A91F65F.EBBFCAF7@mountain.net> (raw)
In-Reply-To: <Pine.GSO.4.30.0102192252130.7963-100000@balu> <Pine.LNX.4.10.10102191421140.4861-100000@master.linux-ide.org> <20010219173153.B12609@ganymede.isdn.uiuc.edu>

Bill Wendling wrote:
> 
> Also sprach Andre Hedrick:
> } On Mon, 19 Feb 2001, Pozsar Balazs wrote:
> }
> } > from drivers/ide/ide-features.c:
> } >
> } > /*
> } >  *  All hosts that use the 80c ribbon mus use!
> } >  */
> } > byte eighty_ninty_three (ide_drive_t *drive)
> } > {
> } >         return ((byte) ((HWIF(drive)->udma_four) &&
> } > #ifndef CONFIG_IDEDMA_IVB
> } >                         (drive->id->hw_config & 0x4000) &&
> } > #endif /* CONFIG_IDEDMA_IVB */
> } >                         (drive->id->hw_config & 0x6000)) ? 1 : 0);
> } > }
> } >
> } > If i see well, then this is always same whether CONFIG_IDEDMA_IVB is
> } > defined or not.
> } > What's the clue?
> }
> [snip...]
> 
> The use of the ternary operator is superfluous, though...and makes the
> code look ugly IMNSHO :).
> 

Check return type. 0 == ((byte) 0x6000).

Tom

  parent reply	other threads:[~2001-02-20  4:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-19 21:57 [IDE] meaningless #ifndef? Pozsar Balazs
2001-02-19 22:31 ` Andre Hedrick
2001-02-19 23:31   ` Bill Wendling
2001-02-19 23:34     ` Andre Hedrick
2001-02-20  4:45     ` Tom Leete [this message]
2001-02-20  5:10     ` Tom Leete
2001-02-20  9:47 ` Andrzej Krzysztofowicz
     [not found] <Pine.LNX.4.21.0102201705280.11260-100000@alloc>
2001-02-20 17:45 ` Hugh Dickins
2001-02-20 18:20   ` Vojtech Pavlik
2001-02-20 19:08     ` Hugh Dickins

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=3A91F65F.EBBFCAF7@mountain.net \
    --to=tleete@mountain.net \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pozsy@sch.bme.hu \
    --cc=wendling@ganymede.isdn.uiuc.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.