From: Anup Patel <anup.patel@broadcom.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: Ankit Jindal <thatsjindal@gmail.com>,
Jan Viktorin <viktorin@rehivetech.com>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
Anup Patel <anup.patel@broadcom.com>
Subject: [PATCH RESEND v2 2/8] uio: code style cleanup
Date: Mon, 8 Aug 2016 11:22:31 +0530 [thread overview]
Message-ID: <1470635557-13416-3-git-send-email-anup.patel@broadcom.com> (raw)
In-Reply-To: <1470635557-13416-1-git-send-email-anup.patel@broadcom.com>
From: Ankit Jindal <thatsjindal@gmail.com>
This patch fixes the indentation of switch-case block in uio driver.
Signed-off-by: Ankit Jindal <thatsjindal@gmail.com>
Signed-off-by: Anup Patel <anup.patel@broadcom.com>
---
drivers/uio/uio.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/uio/uio.c b/drivers/uio/uio.c
index fba021f..f2729b7 100644
--- a/drivers/uio/uio.c
+++ b/drivers/uio/uio.c
@@ -703,13 +703,13 @@ static int uio_mmap(struct file *filep, struct vm_area_struct *vma)
}
switch (idev->info->mem[mi].memtype) {
- case UIO_MEM_PHYS:
- return uio_mmap_physical(vma);
- case UIO_MEM_LOGICAL:
- case UIO_MEM_VIRTUAL:
- return uio_mmap_logical(vma);
- default:
- return -EINVAL;
+ case UIO_MEM_PHYS:
+ return uio_mmap_physical(vma);
+ case UIO_MEM_LOGICAL:
+ case UIO_MEM_VIRTUAL:
+ return uio_mmap_logical(vma);
+ default:
+ return -EINVAL;
}
}
--
1.9.1
next prev parent reply other threads:[~2016-08-08 5:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 5:52 [PATCH RESEND v2 0/8] Cache-coherent DMA access using UIO Anup Patel
2016-08-08 5:52 ` [PATCH RESEND v2 1/8] uio: fix dmem_region_start computation Anup Patel
2016-08-08 5:52 ` Anup Patel [this message]
2016-08-08 5:52 ` [PATCH RESEND v2 3/8] uio: Add new UIO_MEM_PHYS_CACHE type for mem regions Anup Patel
2016-08-08 5:52 ` [PATCH RESEND v2 4/8] uio: Add new UIO_MEM_DEVICE " Anup Patel
2016-08-08 5:52 ` [PATCH RESEND v2 5/8] Documentation: Update documentation for UIO_MEM_PHYS_CACHE and UIO_MEM_DEVICE Anup Patel
2016-08-08 5:52 ` [PATCH RESEND v2 6/8] uio: UIO_IRQ_NONE is a valid option for uioinfo->irq Anup Patel
2016-08-08 5:52 ` [PATCH RESEND v2 7/8] uio: bind uio_dmem_genirq via OF Anup Patel
2016-08-08 5:52 ` [PATCH RESEND v2 8/8] uio: Use new memtypes in uio_dmem_genirq Anup Patel
2016-08-10 15:55 ` [PATCH RESEND v2 0/8] Cache-coherent DMA access using UIO Arnd Bergmann
2016-08-11 4:00 ` Anup Patel
2016-08-11 4:16 ` Alex Williamson
2016-08-11 4:36 ` Anup Patel
2016-08-11 12:29 ` Alex Williamson
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=1470635557-13416-3-git-send-email-anup.patel@broadcom.com \
--to=anup.patel@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=thatsjindal@gmail.com \
--cc=viktorin@rehivetech.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).