From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: bunk@fs.tum.de, acme@conectiva.com.br,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [2.6 patch] atalk compile errors with SYSCTL=n
Date: Wed, 18 Aug 2004 14:47:28 -0700 [thread overview]
Message-ID: <20040818144728.5f5734c4.davem@redhat.com> (raw)
In-Reply-To: <20040811170101.69c140b6@dell_ss3.pdx.osdl.net>
On Wed, 11 Aug 2004 17:01:01 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:
> I prefer to have the CONFIG stuff in the header file.
> Here is an alternative that rearranges to put all function
> prototypes in atalk.h and stubs if necessary. It gets all the #ifdef
> CONFIG_ stuff out of the .c files.
Applied, thanks Stephen.
prev parent reply other threads:[~2004-08-18 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 22:47 [2.6 patch] atalk compile errors with SYSCTL=n Adrian Bunk
2004-08-12 0:01 ` Stephen Hemminger
2004-08-12 8:47 ` Adrian Bunk
2004-08-18 21:47 ` David S. Miller [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=20040818144728.5f5734c4.davem@redhat.com \
--to=davem@redhat.com \
--cc=acme@conectiva.com.br \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=shemminger@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;
as well as URLs for NNTP newsgroup(s).