mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Jean Tourrilhes <jt@bougret.hpl.hp.com>,
	linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
	Adrian Bunk <bunk@fs.tum.de>
Subject: Re: [patch] fix vlsi_ir.c compile if !CONFIG_PROC_FS
Date: Mon, 09 Jun 2003 16:00:57 +1000	[thread overview]
Message-ID: <20030609073355.E92DE2C390@lists.samba.org> (raw)
In-Reply-To: Your message of "Sat, 07 Jun 2003 18:22:39 +0200." <Pine.SOL.4.30.0306071815120.6449-100000@mion.elka.pw.edu.pl>

In message <Pine.SOL.4.30.0306071815120.6449-100000@mion.elka.pw.edu.pl> you write:
> -static inline void remove_proc_entry(const char *name, struct proc_dir_entry *parent) {};
> +#define remove_proc_entry(name, parent)	/* nothing */

> And you wil not have to readd #ifdef/#endif pair.
> 
> I've seen Sam's mail but this is generic solution to quiet compiler
> and will work for any remove_proc_entry() user.

And it'll leave unused warnings all over the place, meaning you have
to add __unused to all the callers.  Now gcc 3.3 will actually discard
those unused functions, this might be worth considering.

But if you're going to do that, make create_proc_entry etc *not*
return NULL if !CONFIG_PROC_FS, otherwise you need the #ifdef anyway.
This has been noted before.

Good luck!
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  parent reply	other threads:[~2003-06-09  7:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-07 15:24 Adrian Bunk
2003-06-07 15:58 ` Sam Ravnborg
2003-06-07 16:13   ` Adrian Bunk
2003-06-08  9:43   ` Martin Diehl
2003-06-07 16:22 ` Bartlomiej Zolnierkiewicz
2003-06-07 16:59   ` Adrian Bunk
2003-06-07 17:09     ` Sam Ravnborg
2003-06-07 20:09   ` Andrew Morton
2003-06-09  6:00   ` Rusty Russell [this message]
2003-06-08  9:40 ` Martin Diehl

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=20030609073355.E92DE2C390@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=bunk@fs.tum.de \
    --cc=jt@bougret.hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@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

all inboxes | Powered by JetHome®