The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dave Airlie <airlied@linux.ie>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [BK tree] [drm] remove counter macros..
Date: Tue, 21 Sep 2004 13:09:36 +0100	[thread overview]
Message-ID: <20040921130936.A22429@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0409211148290.22187@skynet>; from airlied@linux.ie on Tue, Sep 21, 2004 at 11:50:07AM +0100

While I definitly approve this patch is there a specific reason for this
array instead of individual members like

	lock_cnt, open_cnt, close_cnt, etc..?

also the optional counters seem to be largely overlapping, why not always
all four thta exist and if some drivers don't want to update them they'd
just not update them

  reply	other threads:[~2004-09-21 12:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-21 10:50 [BK tree] [drm] remove counter macros Dave Airlie
2004-09-21 12:09 ` Christoph Hellwig [this message]
2004-09-21 12:21   ` Dave Airlie
2004-09-21 12:25     ` Christoph Hellwig

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=20040921130936.A22429@infradead.org \
    --to=hch@infradead.org \
    --cc=airlied@linux.ie \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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