From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Chris Mason <chris.mason@oracle.com>,
Arne Jansen <sensille@gmx.net>,
Andrea Gelmini <andrea.gelmini@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs pull request
Date: Wed, 09 Nov 2011 11:49:38 +0100 [thread overview]
Message-ID: <4EBA5AC2.70403@jan-o-sch.net> (raw)
In-Reply-To: <4EBA560B.1070509@jan-o-sch.net>
On 09.11.2011 11:29, Jan Schmidt wrote:
> "grep bio_add_page fs/btrfs/*.c" will make you unhappy.
Phew. Actually, not that unhappy. Many of the lines seeming to have no
return value check are in fact part of a long or-ed if-statement. Seems
okay after a closer look.
-Jan
next prev parent reply other threads:[~2011-11-09 10:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 18:38 [GIT PULL] Btrfs pull request Chris Mason
2011-11-06 19:29 ` Andrea Gelmini
2011-11-06 19:29 ` Andrea Gelmini
2011-11-07 9:37 ` Arne Jansen
2011-11-07 9:49 ` Roman Mamedov
2011-11-07 9:57 ` Arne Jansen
2011-11-07 12:49 ` Andrea Gelmini
2011-11-07 12:42 ` Andrea Gelmini
2011-11-07 12:45 ` Arne Jansen
2011-11-07 12:50 ` Andrea Gelmini
2011-11-08 7:47 ` Arne Jansen
2011-11-09 1:07 ` Chris Mason
2011-11-09 7:48 ` Christoph Hellwig
2011-11-09 9:06 ` Arne Jansen
2011-11-09 10:11 ` Christoph Hellwig
2011-11-09 12:11 ` Chris Mason
2011-11-09 10:29 ` Jan Schmidt
2011-11-09 10:34 ` Christoph Hellwig
2011-11-09 10:49 ` Jan Schmidt [this message]
2011-11-09 12:12 ` Chris Mason
2011-11-07 0:35 ` Chris Mason
2011-11-08 17:55 ` Dan Merillat
2011-11-08 17:55 ` Dan Merillat
2011-11-08 18:27 ` Chris Mason
2011-11-08 18:27 ` Chris Mason
2011-11-08 20:17 ` Chris Mason
2011-11-08 20:17 ` Chris Mason
2011-11-09 6:53 ` Dan Merillat
2011-11-09 6:53 ` Dan Merillat
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=4EBA5AC2.70403@jan-o-sch.net \
--to=list.btrfs@jan-o-sch.net \
--cc=andrea.gelmini@gmail.com \
--cc=chris.mason@oracle.com \
--cc=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sensille@gmx.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.