From: Gregory Fong <gregory.0xf0@gmail.com>
To: Danesh Petigara <dpetigara@broadcom.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Michal Nazarewicz <mina86@mina86.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-mm@kvack.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: cma: fix CMA aligned offset calculation
Date: Tue, 24 Feb 2015 12:54:38 -0800 [thread overview]
Message-ID: <CADtm3G6UcuLmESz+dFmeMfLfJ=SWwkAiHLUHHKxvmjYTvwZRog@mail.gmail.com> (raw)
In-Reply-To: <1424807759-23311-1-git-send-email-dpetigara@broadcom.com>
[removed stable from cc]
On Tue, Feb 24, 2015 at 11:55 AM, Danesh Petigara
<dpetigara@broadcom.com> wrote:
> diff --git a/mm/cma.c b/mm/cma.c
> index 75016fd..58f37bd 100644
> --- a/mm/cma.c
> +++ b/mm/cma.c
> @@ -70,9 +70,13 @@ static unsigned long cma_bitmap_aligned_offset(struct cma *cma, int align_order)
>
> if (align_order <= cma->order_per_bit)
> return 0;
> - alignment = 1UL << (align_order - cma->order_per_bit);
> - return ALIGN(cma->base_pfn, alignment) -
> - (cma->base_pfn >> cma->order_per_bit);
> +
> + /*
> + * Find a PFN aligned to the specified order and return
> + * an offset represented in order_per_bits.
> + */
> + return (ALIGN(cma->base_pfn, (1UL << align_order))
> + - cma->base_pfn) >> cma->order_per_bit;
It was noticed that this doesn't remove the now-unused 'alignment'
variable, so I think Danesh is planning to submit an updated patch.
Best regards,
Gregory
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-02-24 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 19:55 Danesh Petigara
2015-02-24 20:54 ` Gregory Fong [this message]
2015-02-24 21:10 ` Michal Nazarewicz
2015-02-24 21:43 ` Danesh Petigara
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='CADtm3G6UcuLmESz+dFmeMfLfJ=SWwkAiHLUHHKxvmjYTvwZRog@mail.gmail.com' \
--to=gregory.0xf0@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dpetigara@broadcom.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=mina86@mina86.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