From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
linux-scsi@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Hannes Reinecke <hare@suse.com>,
Johannes Thumshirn <jthumshirn@suse.de>
Subject: Re: [PATCH 3/3] Introduce a type for device information flags, namely bflags_t
Date: Wed, 15 Nov 2017 19:00:24 -0500 [thread overview]
Message-ID: <yq1efozqehz.fsf@oracle.com> (raw)
In-Reply-To: <20171115023317.3595-4-bart.vanassche@wdc.com> (Bart Van Assche's message of "Tue, 14 Nov 2017 18:33:17 -0800")
Bart,
> +typedef __u32 __bitwise bflags_t;
Since we're already out of flags, let's not perpetuate the u32
limitation.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-11-16 0:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 2:33 [PATCH 0/3] Improve device information handling Bart Van Assche
2017-11-15 2:33 ` [PATCH 1/3] device information: Do not interpret error codes as flags Bart Van Assche
2017-11-15 23:57 ` Martin K. Petersen
2017-11-15 2:33 ` [PATCH 2/3] Constify scsi_dev_info_list_add_keyed() string arguments Bart Van Assche
2017-11-15 2:33 ` [PATCH 3/3] Introduce a type for device information flags, namely bflags_t Bart Van Assche
2017-11-16 0:00 ` Martin K. Petersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-15 0:57 [PATCH 0/3] Improve device information handling Bart Van Assche
2017-11-15 0:57 ` [PATCH 3/3] Introduce a type for device information flags, namely bflags_t Bart Van Assche
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=yq1efozqehz.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bart.vanassche@wdc.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--cc=linux-scsi@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