From: Richard Weinberger <richard@nod.at>
To: Camille Constans <camille.constans@parrot.com>,
dedekind1@gmail.com, dwmw2@infradead.org,
computersforpeace@gmail.co, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] UBI: Fix null pointer on error log
Date: Fri, 29 Jul 2016 10:51:13 +0200 [thread overview]
Message-ID: <579B1901.9080004@nod.at> (raw)
In-Reply-To: <1469781852-12253-1-git-send-email-camille.constans@parrot.com>
Camille,
Am 29.07.2016 um 10:44 schrieb Camille Constans:
> It fixes UBI: Extend UBI layer debug/messaging capabilities
> As with this commit ubi_err macro is now:
>
> #define ubi_err(ubi, fmt, ...) pr_err("UBI-%d error: %s: " fmt "\n", \
> ubi->ubi_num, __func__, ##__VA_ARGS__)
>
> It leads to a null pointer when used before allocating ubi.
sorry but a fix for this is already queued:
http://www.spinics.net/lists/stable/msg137428.html
Thanks,
//richard
prev parent reply other threads:[~2016-07-29 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 8:44 [PATCH] UBI: Fix null pointer on error log Camille Constans
2016-07-29 8:51 ` Richard Weinberger [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=579B1901.9080004@nod.at \
--to=richard@nod.at \
--cc=camille.constans@parrot.com \
--cc=computersforpeace@gmail.co \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.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).