From: "Justin P. Mattock" <justinmattock@gmail.com>
To: trivial@kernel.org
Cc: linux-kernel@vger.kernel.org,
"Justin P. Mattock" <justinmattock@gmail.com>
Subject: [RFC V2 07/21]drivers:xen Remove extra semi-colon.
Date: Thu, 24 Mar 2011 13:18:26 -0700 [thread overview]
Message-ID: <1300997920-31573-7-git-send-email-justinmattock@gmail.com> (raw)
In-Reply-To: <1300997920-31573-1-git-send-email-justinmattock@gmail.com>
The patch below removes an extra semi-colon from various parts
of the kernel. Please have a look when you have time, and let
me know if its legit or not.
Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
---
drivers/xen/evtchn.c | 2 +-
drivers/xen/swiotlb-xen.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/xen/evtchn.c b/drivers/xen/evtchn.c
index ef11daf..dbc13e9 100644
--- a/drivers/xen/evtchn.c
+++ b/drivers/xen/evtchn.c
@@ -470,7 +470,7 @@ static int evtchn_open(struct inode *inode, struct file *filp)
filp->private_data = u;
- return nonseekable_open(inode, filp);;
+ return nonseekable_open(inode, filp);
}
static int evtchn_release(struct inode *inode, struct file *filp)
diff --git a/drivers/xen/swiotlb-xen.c b/drivers/xen/swiotlb-xen.c
index 54469c3..65ea21a 100644
--- a/drivers/xen/swiotlb-xen.c
+++ b/drivers/xen/swiotlb-xen.c
@@ -54,7 +54,7 @@ u64 start_dma_addr;
static dma_addr_t xen_phys_to_bus(phys_addr_t paddr)
{
- return phys_to_machine(XPADDR(paddr)).maddr;;
+ return phys_to_machine(XPADDR(paddr)).maddr;
}
static phys_addr_t xen_bus_to_phys(dma_addr_t baddr)
--
1.7.4.1
next prev parent reply other threads:[~2011-03-24 20:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 20:18 [RFC V2 01/21]arch:arm:mach Remove extra semi-colon Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 02/21]arch:ia64 " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 03/21]arch:um:drivers:mmapper_kern.c " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 04/21]arch:s390:hypfs:hypfs.h " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 05/21]drivers:scsi " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 06/21]drivers:leds:leds-mc13783.c " Justin P. Mattock
2011-03-24 20:18 ` Justin P. Mattock [this message]
2011-03-24 20:18 ` [RFC V2 08/21]drivers:tty:serial:mrst_max3110.c " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 09/21]drivers:power:intel_mid_battery.c " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 10/21]drivers:gpio:langwell_gpio.c " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 11/21]drivers:net " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 12/21]drivers:video:mxsfb.c " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 13/21]drivers:i2c:busses:i2c-designware.c " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 14/21]drivers:staging " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 15/21]drivers:target " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 16/21]fs:logfs " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 17/21]kernel:pm_qos_params.c " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 18/21]mm:hugetlb.c " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 19/21]net remove " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 20/21]security:selinux:selinuxfs.c Remove " Justin P. Mattock
2011-03-24 20:18 ` [RFC V2 21/21]tools:power:x86:turbostat:turbostat.c " Justin P. Mattock
2011-04-10 15:09 ` [RFC V2 01/21]arch:arm:mach " Jiri Kosina
2011-04-10 18:49 ` Justin P. Mattock
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=1300997920-31573-7-git-send-email-justinmattock@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
/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