From: Bernd Eckenfels <ecki-news2002-08@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lock assertion macros for 2.5.30
Date: Fri, 9 Aug 2002 06:12:19 +0200 [thread overview]
Message-ID: <E17d18N-0001JZ-00@sites.inka.de> (raw)
In-Reply-To: <E17d04X-0000eD-00@starship>
In article <E17d04X-0000eD-00@starship> you wrote:
> You would just have to break the patch up again when you submit it. You
> might want create a patch that demonstrates its usage, by adding some
> asserts to core code and removing comments where the assert makes them
> redundant.
Yes, I defintely thing that those asserts are a good way of documenting
contracts. They can be used to document when a function expects a lock to be
held, and they will also be able to empirical test, if it is true.
It may even help static code analysers to find places where the assertion
macros are missing.
Greetings
Bernd
next prev parent reply other threads:[~2002-08-09 4:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 20:51 Jesse Barnes
2002-08-07 21:02 ` Rik van Riel
2002-08-07 21:08 ` Jesse Barnes
2002-08-07 21:21 ` Rik van Riel
2002-08-07 21:39 ` Jesse Barnes
2002-08-07 21:44 ` Rik van Riel
2002-08-08 7:58 ` Marcin Dalecki
2002-08-08 11:09 ` Daniel Phillips
2002-08-07 22:15 ` Jesse Barnes
2002-08-07 22:19 ` Rik van Riel
2002-08-08 17:23 ` Jesse Barnes
2002-08-08 17:36 ` Rik van Riel
2002-08-08 17:39 ` Jesse Barnes
2002-08-09 2:56 ` Daniel Phillips
2002-08-12 21:03 ` [PATCH] lock assertion macros for 2.5.31 Jesse Barnes
[not found] ` <3D5829B9.D281B855@zip.com.au>
[not found] ` <20020812223645.GB40343@sgi.com>
[not found] ` <3D5840E9.89C8680C@zip.com.au>
2002-08-21 18:26 ` Jesse Barnes
2002-08-21 18:40 ` Andrew Morton
2002-08-21 18:46 ` Jesse Barnes
2002-08-09 3:04 ` [PATCH] lock assertion macros for 2.5.30 Daniel Phillips
2002-08-09 4:12 ` Bernd Eckenfels [this message]
2002-08-07 22:30 ` Daniel Phillips
2002-08-07 22:41 ` Roman Zippel
2002-08-08 0:07 ` Thunder from the hill
2002-08-07 21:37 ` Oliver Xymoron
2002-08-08 12:55 ` Joshua MacDonald
2002-08-08 13:23 ` Jens Axboe
2002-08-08 6:00 ` Jens Axboe
2002-08-08 17:08 ` Jesse Barnes
2002-08-08 17:31 ` Rik van Riel
2002-08-08 17:35 ` Jesse Barnes
2002-08-08 17:43 ` Joshua MacDonald
2002-08-08 17:47 ` Rik van Riel
[not found] <0C01A29FBAE24448A792F5C68F5EA47D2D4437@nasdaq.ms.ensim.com>
2002-08-08 18:52 ` Paul Menage
2002-08-08 19:00 ` Rik van Riel
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=E17d18N-0001JZ-00@sites.inka.de \
--to=ecki-news2002-08@lina.inka.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
all inboxes | Powered by JetHome®