public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed L Cashin <ecashin@coraid.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ATA over Ethernet driver for 2.6.9 (with changes)
Date: Tue, 14 Dec 2004 08:50:12 -0500	[thread overview]
Message-ID: <87is75oup7.fsf@coraid.com> (raw)
In-Reply-To: 20041213215434.GA22215@kroah.com

Greg KH <greg@kroah.com> writes:

...
>> +enum {
>> +	DEVFL_UP = 1,	/* device is installed in system and ready for AoE->ATA commands */
>> +	DEVFL_TKILL = (1<<1),	/* flag for timer to know when to kill self */
>> +	DEVFL_EXT = (1<<2),	/* device accepts lba48 commands */
>> +	DEVFL_CLOSEWAIT = (1<<3), /* device is waiting for all closes to revalidate */
>> +	DEVFL_WC_UPDATE = (1<<4), /* this device needs to update write cache status */
>> +	DEVFL_WORKON = (1<<4),
>> +
>> +	BUFFL_FAIL = 1,
>> +};
>
> Any reason why BUFFL_FAIL and DEVFL_UP are the same value?  It looks
> like they can be used in the same variable right?

The struct Buf and the struct Aoedev both have a flags member.
BUFFL_* is for the flags member of the Buf, while DEVFL_* are bits for
the flags member of the struct Aoedev.

Although they both happen to be 1, they are conceptually unrelated, so
they have different names.  They should not be used in the same
variable.  BUFFL_ for the flags of a struct Buf, and DEVFL_ for the
flags of a struct Aoedev.

>
> The class_simple stuff looked sane, nice job.

Thanks!  It was pretty easy.

-- 
  Ed L Cashin <ecashin@coraid.com>


      reply	other threads:[~2004-12-14 13:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-13 16:04 [PATCH] ATA over Ethernet driver for 2.6.9 (with changes) Ed L Cashin
2004-12-13 20:19 ` Jens Axboe
2004-12-14 13:39   ` Ed L Cashin
2004-12-14 13:52     ` Jens Axboe
2004-12-13 21:23 ` Jan-Benedict Glaw
2004-12-14 20:39   ` Ed L Cashin
2004-12-13 21:54 ` Greg KH
2004-12-14 13:50   ` Ed L Cashin [this message]

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=87is75oup7.fsf@coraid.com \
    --to=ecashin@coraid.com \
    --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