From: Diego Calleja <diegocg@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH] __must_check btrfs_alloc_path()
Date: Mon, 29 Dec 2008 22:02:04 +0100 [thread overview]
Message-ID: <20081229220204.65d99bb1@diego-desktop> (raw)
IMHO it's a good thing to add __must_check in new code where it has sense.
Index: btrfs-unstable-standalone/ctree.c
===================================================================
--- btrfs-unstable-standalone.orig/ctree.c 2008-12-29 21:57:15.366588465 +0100
+++ btrfs-unstable-standalone/ctree.c 2008-12-29 21:58:06.878588402 +0100
@@ -43,7 +43,7 @@
memset(p, 0, sizeof(*p));
}
-struct btrfs_path *btrfs_alloc_path(void)
+struct btrfs_path __must_check *btrfs_alloc_path(void)
{
struct btrfs_path *path;
path = kmem_cache_alloc(btrfs_path_cachep, GFP_NOFS);
next reply other threads:[~2008-12-29 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 21:02 Diego Calleja [this message]
2009-01-05 15:34 ` [PATCH] __must_check btrfs_alloc_path() Chris Mason
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=20081229220204.65d99bb1@diego-desktop \
--to=diegocg@gmail.com \
--cc=linux-btrfs@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