From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Cc: linux-f2fs-devel@lists.sourceforge.net, kernel-janitors@vger.kernel.org
Subject: Re: [patch] f2fs: alloc_page() doesn't return an ERR_PTR
Date: Wed, 14 Aug 2013 13:56:13 +0000 [thread overview]
Message-ID: <20130814135613.GF4713@mwanda> (raw)
In-Reply-To: <1376486676.2354.5.camel@kjgkr>
On Wed, Aug 14, 2013 at 10:24:36PM +0900, Jaegeuk Kim wrote:
> Hi Dan,
>
> Agreed.
> Could you make a patch that covers other alloc_page cases too?
Sure. Thanks for catching that. I will resend a v2 of this one
which fixes those as well.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Cc: linux-f2fs-devel@lists.sourceforge.net, kernel-janitors@vger.kernel.org
Subject: Re: [patch] f2fs: alloc_page() doesn't return an ERR_PTR
Date: Wed, 14 Aug 2013 16:56:13 +0300 [thread overview]
Message-ID: <20130814135613.GF4713@mwanda> (raw)
In-Reply-To: <1376486676.2354.5.camel@kjgkr>
On Wed, Aug 14, 2013 at 10:24:36PM +0900, Jaegeuk Kim wrote:
> Hi Dan,
>
> Agreed.
> Could you make a patch that covers other alloc_page cases too?
Sure. Thanks for catching that. I will resend a v2 of this one
which fixes those as well.
regards,
dan carpenter
next prev parent reply other threads:[~2013-08-14 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 11:41 [patch] f2fs: alloc_page() doesn't return an ERR_PTR Dan Carpenter
2013-08-14 11:41 ` Dan Carpenter
2013-08-14 13:24 ` Jaegeuk Kim
2013-08-14 13:24 ` Jaegeuk Kim
2013-08-14 13:56 ` Dan Carpenter [this message]
2013-08-14 13:56 ` Dan Carpenter
2013-08-15 5:54 ` [patch v2] " Dan Carpenter
2013-08-15 5:54 ` Dan Carpenter
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=20130814135613.GF4713@mwanda \
--to=dan.carpenter@oracle.com \
--cc=jaegeuk.kim@samsung.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.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.