linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] AFS: afs_voltypes isn't always required (fwd)
Date: Mon, 13 Dec 2004 14:52:10 +0000	[thread overview]
Message-ID: <4659.1102949530@redhat.com> (raw)
In-Reply-To: <20041211165451.GT22324@stusta.de>


Adrian Bunk <bunk@stusta.de> wrote:

> afs_voltypes is only used #ifdef __KDEBUG, and even then it doesn't has 
> to be a global symbol.

I supposed I can always add this back with the next patch if I need it
then. It's currently used for a /proc file in my under-development code.

David

  reply	other threads:[~2004-12-13 14:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-11 16:54 [2.6 patch] AFS: afs_voltypes isn't always required (fwd) Adrian Bunk
2004-12-13 14:52 ` David Howells [this message]
2004-12-18  0:33   ` Adrian Bunk

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=4659.1102949530@redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).