From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Konrad Rzeszutek Wilk <konrad@darnok.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Mike Christie <michaelc@cs.wisc.edu>,
Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
James Bottomley <James.Bottomley@suse.de>,
Jens Axboe <axboe@kernel.dk>, Boaz Harrosh <bharrosh@panasas.com>
Subject: Re: [RFC 04/22] tcm: Add v4 base data structures and struct target_core_fabric_ops
Date: Tue, 07 Sep 2010 18:44:20 -0700 [thread overview]
Message-ID: <1283910260.556.393.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <201009071656.21568.konrad@darnok.org>
On Tue, 2010-09-07 at 16:56 -0400, Konrad Rzeszutek Wilk wrote:
> > Hi Konard,
> >
> > I just pushed most of your recommend cleanups for target_core_base.h to
> > lio-core-2.6.git/lio-4.0. The cleanup series has been posted on
> > lio-devel list to prevent extra noise on linux-scsi, et al, but for
> > reference the shortlog and diffstat are attached below.. I did not dive
> > into intermixed struct + #defines, but I am still pretty indifferent on
> > this particular item.
> >
>
> So the reasons why I thought it would be a good idea to combine the #defines
> and the values and also dropping the prefix of structs for all of the 'flag'
> members is that:
>
> 1) once you have them intermixed, searching for a particular flag either using
> cscope/ctags becomes easier. You have the definition of the 'flag' and the
> different values it can have in one localized spot. It also removes your
> worry about the 'grep' - you usually search for the values that a specific
> flag has and if you use that tool you can find it right there along with the
> structure it was defined in.
>
> 2). From a perspective of a vendor maintainer who has to find a fix, getting
> familiarized with the code within a short window time frame and having the
> acceptable states and its definitions in one place (and even pointers to the
> specs if there are some) makes it sooo much easier to grok the code.
> Having even nice ascii art of how/what works together is even better.
Ok, I think these are both reasonable points for combining the #defines
near the structure members where they are actually used. I will go
ahead and make this change, but I would still like to keep the exiting
prefixes for structure members for now.
Thanks for your comments Konrad!
--nab
prev parent reply other threads:[~2010-09-08 1:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 9:20 Nicholas A. Bellinger
2010-09-02 5:56 ` Konrad Rzeszutek Wilk
2010-09-02 19:19 ` Nicholas A. Bellinger
2010-09-04 23:53 ` Nicholas A. Bellinger
2010-09-05 0:35 ` ldd scull_load question runcoderen
2010-09-05 0:43 ` Randy Dunlap
2010-09-05 1:01 ` runcoderen
2010-09-05 21:20 ` Randy Dunlap
2010-09-05 3:21 ` Adam Jiang
2010-09-07 20:56 ` [RFC 04/22] tcm: Add v4 base data structures and struct target_core_fabric_ops Konrad Rzeszutek Wilk
2010-09-08 1:44 ` Nicholas A. Bellinger [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=1283910260.556.393.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=James.Bottomley@suse.de \
--cc=axboe@kernel.dk \
--cc=bharrosh@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®