From: Richard Knutsson <ricknu-0@student.ltu.se>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, jgarzik@pobox.com,
ashutosh.naik@gmail.com
Subject: Re: [PATCH -mm2] net: Fix compiler-error on dgrs.c when !CONFIG_PCI
Date: Tue, 22 Nov 2005 00:20:30 +0100 [thread overview]
Message-ID: <4382563E.50502@student.ltu.se> (raw)
In-Reply-To: <E1EeJu8-0006vr-00@gondolin.me.apana.org.au>
Herbert Xu wrote:
>Richard Knutsson <ricknu-0@student.ltu.se> wrote:
>
>
>>We need it even if pci_register_driver() and pci_register_driver() is
>>empty shells. And instead of removing #endif CONFIG_PCI for
>>
>>
>
>I don't think so. Please see my previous patch where pci_register_driver
>is not called at all if CONFIG_PCI is not defined.
>
>Cheers,
>
>
Yes, I know you patch don't need it (thought you commented the patch vs.
dgrs.c, not vs. you patch). But to do that, you have to introduce a new
dgrs-specific pci-layer to compensate. If you don't want to have an
empty struct, is it not nicer/easier to just #ifdef CONFIG_PCI the
pci_*-functions? (instead of two inline functions for every used
pci_*-function?)
Am thinking of removing the #ifdef CONFIG_PCI's in other files, to
"clean up" the code, but that would introduce this problem again, don't
you think it is more readable to make an empty struct when !CONFIG_PCI,
then making new pci_*-functions specific to the driver?
cu
next prev parent reply other threads:[~2005-11-21 23:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 1:39 [PATCH -mm2] net: Fix compiler-error on dgrs.c when !CONFIG_PCI Richard Knutsson
2005-11-20 10:24 ` Herbert Xu
2005-11-20 15:35 ` Richard Knutsson
2005-11-20 20:40 ` Herbert Xu
2005-11-21 12:52 ` Richard Knutsson
2005-11-21 20:37 ` Herbert Xu
2005-11-21 21:47 ` Richard Knutsson
2005-11-21 22:12 ` Herbert Xu
2005-11-21 23:20 ` Richard Knutsson [this message]
2005-11-21 23:36 ` Herbert Xu
2005-11-22 1:56 ` Richard Knutsson
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=4382563E.50502@student.ltu.se \
--to=ricknu-0@student.ltu.se \
--cc=akpm@osdl.org \
--cc=ashutosh.naik@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.