From: Artem Bityutskiy <dedekind1@gmail.com>
To: Roman Tereshonkov <roman.tereshonkov@nokia.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtdoops: fix the oops_page_used array size
Date: Thu, 08 Dec 2011 23:58:27 +0200 [thread overview]
Message-ID: <1323381509.2074.5.camel@koala> (raw)
In-Reply-To: <20111207152537.GA8719@nokia.com>
On Wed, 2011-12-07 at 17:25 +0200, Roman Tereshonkov wrote:
> BITS_PER_LONG is equal to 32.
> If we want to allocate memory for 32 pages with one bit per page then
> 32 / BITS_PER_LONG is equal to 1 byte that is 8 bits.
> To fix it we need to multiply the result by sizeof(unsigned long)
> equal to 4.
Ah, you are right. This should also go to the stable tree, I've
added Cc: stable@kernel.org
Pushed to l2-mtd-2.6.git thanks.
Artem.
prev parent reply other threads:[~2011-12-08 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 10:49 [PATCH] mtdoops: fix the oops_page_used array size Roman Tereshonkov
2011-12-04 13:44 ` Artem Bityutskiy
2011-12-07 15:25 ` Roman Tereshonkov
2011-12-08 21:58 ` 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=1323381509.2074.5.camel@koala \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=roman.tereshonkov@nokia.com \
/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).