From: Thomas Meyer <thomas@m3y3r.de>
To: monstr@monstr.eu, linux-kernel@vger.kernel.org
Subject: [PATCH 4/7] microblaze: Cocci spatch "vma_pages"
Date: Thu, 21 Sep 2017 00:29:36 +0200 [thread overview]
Message-ID: <1505946334393-235092379-4-diffsplit-thomas@m3y3r.de> (raw)
In-Reply-To: <1505946334393-568186305-0-diffsplit-thomas@m3y3r.de>
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;
next prev parent reply other threads:[~2017-09-20 22:40 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 2/7] arm64: " Thomas Meyer
2017-09-26 11:57 ` Robin Murphy
2017-09-20 22:29 ` Thomas Meyer [this message]
2017-09-25 13:37 ` [PATCH 4/7] microblaze: " Michal Simek
2017-09-20 22:29 ` [PATCH 6/7] KVM: PPC: " Thomas Meyer
2017-10-19 3:46 ` Paul Mackerras
2017-09-20 22:29 ` [PATCH 1/7] ARM: dma-mapping: " Thomas Meyer
2017-09-20 22:29 ` [PATCH 5/7] MIPS: " Thomas Meyer
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=1505946334393-235092379-4-diffsplit-thomas@m3y3r.de \
--to=thomas@m3y3r.de \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
/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®