From: Juan Quintela <quintela@mandrakesoft.com>
To: Jens Axboe <axboe@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] only use 48-bit lba when necessary
Date: Fri, 04 Apr 2003 17:48:20 +0200 [thread overview]
Message-ID: <86wuia1cxn.fsf@trasno.mitica> (raw)
In-Reply-To: <20030404132214.GC786@suse.de> (Jens Axboe's message of "Fri, 4 Apr 2003 15:22:14 +0200")
Hi
jens> + if (drive->addressing == 1 && block > 0xfffffff)
jens> + lba48 = 1;
jens> +
>>
>> lba48 = (drive->addressing == 1) && (block > 0xfffffff);
>>
>> should do the trick.
jens> I'm not going to use such nonsense, sorry. The spelled out versions are
jens> a lot more readable. The command ?: constructs used in ide-disk are a
jens> joke, imo.
Read it again, please. Told me wehre are the ?: command.
Reason is that:
if (expr)
var = true;
else
var = false;
is always a bad construct.
var = expr;
is a better construct to express that meaning.
And yes, your is a variation of the same theme:
var = false;
if (expr)
var = true;
Later, Juan "who also didn't like ?: operator"
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
next prev parent reply other threads:[~2003-04-04 15:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 12:29 [PATCH] only use 48-bit lba when necessary Jens Axboe
2003-04-04 13:19 ` Juan Quintela
2003-04-04 13:22 ` Jens Axboe
2003-04-04 15:48 ` Juan Quintela [this message]
2003-04-04 15:54 ` Jens Axboe
2003-04-04 17:06 ` John Bradford
2003-04-04 14:40 ` Andries Brouwer
2003-04-04 15:13 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2003-04-04 17:02 Chuck Ebbert
2003-04-17 14:20 ` Matt Mackall
2003-04-17 15:24 ` Timothy Miller
2003-04-17 16:05 ` Matt Mackall
2003-04-17 18:49 ` Timothy Miller
2003-04-18 1:34 Chuck Ebbert
2003-04-18 4:18 ` Matt Mackall
2003-04-18 14:34 ` Timothy Miller
2003-04-18 3:32 linux-kernel
2003-04-18 9:50 Chuck Ebbert
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=86wuia1cxn.fsf@trasno.mitica \
--to=quintela@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=linux-kernel@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