netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mitchell Blank Jr <mitch@sfgoth.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: chas williams <chas@cmf.nrl.navy.mil>,
	davem@redhat.com, netdev@oss.sgi.com
Subject: Re: [PATCH][ATM]: [lanai] ioctl only meant for debugging (from mitch@sfgoth.com)
Date: Mon, 22 Sep 2003 21:45:11 -0700	[thread overview]
Message-ID: <20030923044511.GB15907@gaz.sfgoth.com> (raw)
In-Reply-To: <20030922190017.A27677@infradead.org>

Christoph Hellwig wrote (in two different emails):
> Umm, shouldn't you just ifdef out the whole function and it's
> assignment to the operations vector?  This looks horribly ugly..

Sorry for any ugliness - its my fault.  I personally don't think it really
makes a difference either way.  Its already #ifdef'ed the same way in 2.6.

> and
> third your (void)arg crap is ugly as hell. (what compiler do you have
> that complains about this, btw, gcc 3.3 doesn't..).

"gcc -Wunused-parameter"

It's true that the kernel doesn't compile with that option but I've gotten
in the habit of adding the "(void) x;" from working on other projects that
do.  I think it's pretty harmless.

> #if FOO
> foo_ioctl()
> {
> }
> #else
> #define foo_ioctl	NULL
> #endif

Yes, that would probably be (a bit) cleaner.  That's what we already
use for lanai_proc_read if !CONFIG_PROC_FS

-Mitch

  reply	other threads:[~2003-09-23  4:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22 17:03 [PATCH][ATM]: [lanai] ioctl only meant for debugging (from mitch@sfgoth.com) chas williams
2003-09-22 17:07 ` Christoph Hellwig
2003-09-22 17:55   ` chas williams
2003-09-22 18:00     ` Christoph Hellwig
2003-09-23  4:45       ` Mitchell Blank Jr [this message]
2003-09-23 10:57     ` David S. Miller
2003-09-23 11:42       ` chas williams

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=20030923044511.GB15907@gaz.sfgoth.com \
    --to=mitch@sfgoth.com \
    --cc=chas@cmf.nrl.navy.mil \
    --cc=davem@redhat.com \
    --cc=hch@infradead.org \
    --cc=netdev@oss.sgi.com \
    /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).