The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: kaos@ocs.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: Unix-domain sockets - abstract addresses
Date: Fri, 09 Aug 2002 18:41:04 -0700 (PDT)	[thread overview]
Message-ID: <20020809.184104.68900725.davem@redhat.com> (raw)
In-Reply-To: <8740.1028943304@ocs3.intra.ocs.com.au>

   From: Keith Owens <kaos@ocs.com.au>
   Date: Sat, 10 Aug 2002 11:35:04 +1000
   
   af_unix.c is linked into unix.o so we have -DKBUILD_MODNAME=unix.  Alas
   we also have -Dunix=1.  __stringify(KBUILD_MODNAME) -> __stringify(unix) ->
   "1" instead of "unix".
   
This seems really tacky.  There must be a better way to do this.
Perhaps prepending some constant string prefix to these module
names such that they will not collide with the namespace in
this way.  For example, "kmod_".

  reply	other threads:[~2002-08-10  1:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08 16:15 Unix-domain sockets - abstract addresses Michael Procter
2002-08-08 18:36 ` kuznet
2002-08-09  0:29   ` Thunder from the hill
2002-08-09 13:52   ` Michael Procter
2002-08-09 16:15     ` kuznet
2002-08-09 22:33     ` Thunder from the hill
2002-08-10  1:05       ` David S. Miller
2002-08-10  1:35         ` Keith Owens
2002-08-10  1:41           ` David S. Miller [this message]
2002-08-10  2:19             ` Keith Owens
2002-08-10  2:15               ` David S. Miller
2002-08-10 10:59               ` Roman Zippel
2002-08-12  2:35               ` Oliver Xymoron
2002-08-12  2:59                 ` Keith Owens
2002-08-12  2:59                   ` David S. Miller
2002-08-12  3:20                     ` Keith Owens
2002-08-12  3:13                       ` David S. Miller
2002-08-12  3:57                         ` Keith Owens
2002-08-12  7:13                           ` Eric W. Biederman
2002-08-12 14:28                           ` David Woodhouse
2002-08-10  6:29         ` Thunder from the hill

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=20020809.184104.68900725.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=kaos@ocs.com.au \
    --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