From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Richard Weinberger <richard@nod.at>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH for v3.15 0/2] UBI: block: Support very large volumes
Date: Mon, 5 May 2014 06:24:04 -0300 [thread overview]
Message-ID: <20140505092403.GB2873@arch.cereza> (raw)
In-Reply-To: <1399274592.15290.12.camel@sauron.fi.intel.com>
On 05 May 10:23 AM, Artem Bityutskiy wrote:
> On Mon, 2014-05-05 at 09:36 +0300, Artem Bityutskiy wrote:
> > On Wed, 2014-04-23 at 20:59 -0300, Ezequiel Garcia wrote:
> > > > drivers/mtd/ubi/block.c | 10 ++++++----
> > > > 1 file changed, 6 insertions(+), 4 deletions(-)
> > > >
> > >
> > > Do you think you can pick this for v3.15-rc3?
> >
> > Picked both, I'll send them to Linus soon, thanks!
>
> So kbuild caught a warning. Shame I did not notice this myself, but the
> warning indicates a bigger problem - the entire function is not allowed
> to fail, but it seems like there are conditions when it needs to fail.
> Would you please analyze the error handling in the resize path?
>
Working on it.
Sorry for the crap,
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-05-05 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 13:23 [PATCH for v3.15 0/2] UBI: block: Support very large volumes Ezequiel Garcia
2014-04-17 13:23 ` [PATCH 1/2] UBI: block: Set disk_capacity out of the mutex Ezequiel Garcia
2014-04-17 13:23 ` [PATCH 2/2] UBI: block: Avoid disk size integer overflow Ezequiel Garcia
2014-04-23 23:59 ` [PATCH for v3.15 0/2] UBI: block: Support very large volumes Ezequiel Garcia
2014-05-05 6:36 ` Artem Bityutskiy
2014-05-05 7:23 ` Artem Bityutskiy
2014-05-05 9:24 ` Ezequiel Garcia [this message]
2014-05-05 9:46 ` Ezequiel Garcia
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=20140505092403.GB2873@arch.cereza \
--to=ezequiel.garcia@free-electrons.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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