From: Artem Bityutskiy <dedekind1@gmail.com>
To: Kulikov Vasiliy <segooon@gmail.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Julia Lawall <julia@diku.dk>, Tejun Heo <tj@kernel.org>,
linux-mtd@lists.infradead.org,
Adrian Hunter <adrian.hunter@nokia.com>
Subject: Re: [PATCH 11/14] ubifs: check return code of ubifs_lpt_lookup
Date: Tue, 07 Sep 2010 12:32:39 +0300 [thread overview]
Message-ID: <1283851959.2979.27.camel@localhost> (raw)
In-Reply-To: <1283711580-7546-1-git-send-email-segooon@gmail.com>
On Sun, 2010-09-05 at 22:33 +0400, Kulikov Vasiliy wrote:
> From: Vasiliy Kulikov <segooon@gmail.com>
>
> Function ubifs_lpt_lookup may return ERR_PTR(...). Check for it.
>
> Signed-off-by: Vasiliy Kulikov <segooon@gmail.com>
> ---
Pushed both patches to the UBIFS tree, thanks:
http://git.infradead.org/ubifs-2.6.git
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-09-07 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 18:33 [PATCH 11/14] ubifs: check return code of ubifs_lpt_lookup Kulikov Vasiliy
2010-09-07 9:32 ` Artem Bityutskiy [this message]
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=1283851959.2979.27.camel@localhost \
--to=dedekind1@gmail.com \
--cc=adrian.hunter@nokia.com \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=segooon@gmail.com \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).