From: Aubin LaBrosse <aubin@stormboxes.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] Replace assert() with WARN_ON in drivers/scsi/libata-core.c
Date: Mon, 13 Feb 2006 19:20:38 -0500 [thread overview]
Message-ID: <43F12256.1050702@stormboxes.com> (raw)
In-Reply-To: <43F119D0.5080103@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
Jeff Garzik wrote:
> Aubin LaBrosse wrote:
>> Replace assert() with WARN_ON in drivers/scsi/libata-core.c
>>
>> This is my first patch to the kernel - this work was suggested by
>> Jeff Garzik as a janitorial task for libata. If I could get some
>> feedback letting me know that this is the correct format and my tools
>> are setup right, I'll do the rest of these.
>>
>> Signed-off-by: Aubin LaBrosse <aubin@stormboxes.com>
>> ---
>>
>> drivers/scsi/libata-core.c | 46
>> ++++++++++++++++++++++----------------------
>> 1 files changed, 23 insertions(+), 23 deletions(-)
>
> Someone already beat you to it :)
>
> I looked over your patch anyway. It looks acceptable, except we avoid
> the '~' style in such tests:
>
> + WARN_ON(qc == NULL); /* ata_qc_from_tag _might_ return NULL */
> + WARN_ON(~qc->flags & ATA_QCFLAG_ACTIVE);
>
> Jeff
>
So what would be the proper way to invert that type of test? (!(field &
flag)) will do the same, right? is that preferred for anything other
than aesthetic reasons? (which is a fine reason to prefer something, of
course, I'm just wondering if there's any other reasons, performance or
otherwise
-aubin
[-- Attachment #2: aubin.vcf --]
[-- Type: text/x-vcard, Size: 160 bytes --]
begin:vcard
fn:Aubin LaBrosse
n:LaBrosse;Aubin
email;internet:aubin@stormboxes.com
tel;work:589-0692
tel;home:429-1520
tel;cell:493-0121
version:2.1
end:vcard
next prev parent reply other threads:[~2006-02-14 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 23:35 [PATCH] Replace assert() with WARN_ON in drivers/scsi/libata-core.c Aubin LaBrosse
2006-02-13 23:44 ` Jeff Garzik
2006-02-14 0:20 ` Aubin LaBrosse [this message]
2006-02-13 23:45 ` Randy.Dunlap
2006-02-13 23:56 ` Aubin LaBrosse
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=43F12256.1050702@stormboxes.com \
--to=aubin@stormboxes.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).