The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: olaf+list.linux-kernel@olafdietsche.de, eike-kernel@sf-tec.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.16-rc1-git4] accessfs: a permission managing filesystem
Date: Mon, 30 Jan 2006 01:16:30 -0800	[thread overview]
Message-ID: <20060130011630.60f402d8.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0601301006240.6405@yvahk01.tjqt.qr>

Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
>
> 
> >> +static DECLARE_MUTEX(accessfs_sem);
> >
> >Please use a `struct mutex'.
> 
> You know what's irritating? That DECLARE_MUTEX starts a semaphore and
> DEFINE_MUTEX a mutex.
> 

DECLARE_MUTEX will go away.

  reply	other threads:[~2006-01-30  9:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-14 21:06 [PATCH] 2.6.15: access permission filesystem 0.17 Olaf Dietsche
2006-01-14 22:45 ` Ingo Oeser
2006-01-15 21:22   ` Olaf Dietsche
2006-01-23 11:57 ` Rolf Eike Beer
2006-01-28 22:27   ` [PATCH 2.6.16-rc1-git4] accessfs: a permission managing filesystem Olaf Dietsche
2006-01-28 23:01     ` Andrew Morton
2006-01-29 22:47       ` Olaf Dietsche
2006-01-30  9:07       ` Jan Engelhardt
2006-01-30  9:16         ` Andrew Morton [this message]
2006-01-30  9:24           ` Jan Engelhardt
2006-01-30  9:32             ` Andrew Morton
2006-01-30  9:46             ` Arjan van de Ven
2006-01-30  9:51               ` Jan Engelhardt
2006-01-30  9:54                 ` Arjan van de Ven
2006-01-30 10:25                   ` Jan Engelhardt
2006-01-30 10:31                     ` Arjan van de Ven
2006-01-30 10:36                       ` Jan Engelhardt
2006-01-30 10:39                         ` Arjan van de Ven
2006-01-30 10:46                           ` Jan Engelhardt

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=20060130011630.60f402d8.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=eike-kernel@sf-tec.de \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf+list.linux-kernel@olafdietsche.de \
    /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