From: Michal Simek <monstr@monstr.eu>
To: Thomas Meyer <thomas@m3y3r.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/7] microblaze: Cocci spatch "vma_pages"
Date: Mon, 25 Sep 2017 15:37:15 +0200 [thread overview]
Message-ID: <f5343862-0fbe-01b8-7034-035aa96535d5@monstr.eu> (raw)
In-Reply-To: <1505946334393-235092379-4-diffsplit-thomas@m3y3r.de>
[-- Attachment #1.1: Type: text/plain, Size: 1076 bytes --]
On 21.9.2017 00:29, Thomas Meyer wrote:
> Use vma_pages function on vma object instead of explicit computation.
> Found by coccinelle spatch "api/vma_pages.cocci"
>
> Signed-off-by: Thomas Meyer <thomas@m3y3r.de>
> ---
>
> diff -u -p a/arch/microblaze/kernel/dma.c b/arch/microblaze/kernel/dma.c
> --- a/arch/microblaze/kernel/dma.c
> +++ b/arch/microblaze/kernel/dma.c
> @@ -165,7 +165,7 @@ int dma_direct_mmap_coherent(struct devi
> unsigned long attrs)
> {
> #ifdef CONFIG_MMU
> - unsigned long user_count = (vma->vm_end - vma->vm_start) >> PAGE_SHIFT;
> + unsigned long user_count = vma_pages(vma);
> unsigned long count = PAGE_ALIGN(size) >> PAGE_SHIFT;
> unsigned long off = vma->vm_pgoff;
> unsigned long pfn;
>
Applied to mb/next.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2017-09-25 13:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 22:29 [PATCH 0/7] Cocci spatch "vma_pages" - v4.14-rc1 Thomas Meyer
2017-09-20 22:29 ` [PATCH 3/7] metag: Cocci spatch "vma_pages" Thomas Meyer
2017-09-20 22:29 ` [PATCH 7/7] drm/rockchip: " Thomas Meyer
2017-09-21 1:02 ` Mark yao
2017-09-26 5:12 ` Daniel Vetter
2017-09-26 6:33 ` Mark yao
2017-09-26 8:08 ` Daniel Vetter
2017-09-26 9:06 ` Mark yao
2017-09-20 22:29 ` [PATCH 4/7] microblaze: " Thomas Meyer
2017-09-25 13:37 ` Michal Simek [this message]
2017-09-20 22:29 ` [PATCH 2/7] arm64: " Thomas Meyer
2017-09-26 11:57 ` Robin Murphy
2017-09-20 22:29 ` [PATCH 5/7] MIPS: " Thomas Meyer
2017-09-20 22:29 ` [PATCH 1/7] ARM: dma-mapping: " Thomas Meyer
2017-09-20 22:29 ` [PATCH 6/7] KVM: PPC: " Thomas Meyer
2017-10-19 3:46 ` Paul Mackerras
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=f5343862-0fbe-01b8-7034-035aa96535d5@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@m3y3r.de \
/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
all inboxes | Powered by JetHome®