From: Dan Carpenter <dan.carpenter@oracle.com>
To: Arne Jansen <sensille@gmx.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs: initial readahead code and prototypes
Date: Thu, 17 May 2012 16:46:13 +0300 [thread overview]
Message-ID: <20120517134613.GN16999@mwanda> (raw)
In-Reply-To: <4FB4FDC6.5070306@gmx.net>
On Thu, May 17, 2012 at 03:31:50PM +0200, Arne Jansen wrote:
> The assumption here is that if err == 0, eb is always != NULL. There's
> even a tiny comment above the function stating this:
>
> 107 /* in case of err, eb might be NULL */
>
Ah, right. I missed the comment.
> This code changes significantly with the patch
>
> btrfs: extend readahead interface
>
> Where it is written in a more obvious way.
Cool.
regards,
dan carpenter
next prev parent reply other threads:[~2012-05-17 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 7:14 btrfs: initial readahead code and prototypes Dan Carpenter
2012-05-17 13:31 ` Arne Jansen
2012-05-17 13:46 ` Dan Carpenter [this message]
2012-05-17 15:33 ` Arne Jansen
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=20120517134613.GN16999@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox