From: davidb@codeaurora.org (David Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 5/5] RFC: msm: sps: Smart Peripheral System (SPS) driver.
Date: Tue, 01 Mar 2011 12:11:45 -0800 [thread overview]
Message-ID: <8yahbbmvbwe.fsf@huya.qualcomm.com> (raw)
In-Reply-To: <1298941892-25173-6-git-send-email-kheitke@codeaurora.org> (Kenneth Heitke's message of "Mon, 28 Feb 2011 18:11:32 -0700")
On Mon, Feb 28 2011, Kenneth Heitke wrote:
> diff --git a/arch/arm/mach-msm/include/mach/msm_sps.h b/arch/arm/mach-msm/include/mach/msm_sps.h
> +
> diff --git a/arch/arm/mach-msm/sps/Makefile b/arch/arm/mach-msm/sps/Makefile
> +
> diff --git a/arch/arm/mach-msm/sps/sps.c b/arch/arm/mach-msm/sps/sps.c
> +
> diff --git a/arch/arm/mach-msm/sps/sps_bam.c b/arch/arm/mach-msm/sps/sps_bam.c
> +
These four files add spurious blank lines to the end of their files. If
there are no other changes to the patches, I can fix this up before
applying the patches. Otherwise, please remove these before resending
the patches.
Thanks,
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
prev parent reply other threads:[~2011-03-01 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1298941892-25173-1-git-send-email-kheitke@codeaurora.org>
2011-03-01 1:11 ` [RFC PATCH 1/5] RFC: msm: sps: Bus Access Manager (BAM) Hardware driver Kenneth Heitke
2011-03-01 1:11 ` [RFC PATCH 2/5] RFC: msm: sps: BAM-DMA driver Kenneth Heitke
2011-03-01 1:11 ` [RFC PATCH 3/5] RFC: msm: sps: Pipe Memory Manager Kenneth Heitke
2011-03-01 1:11 ` [RFC PATCH 4/5] RFC: msm: sps: Smart Peripheral Subsystem (SPS) Resource Manager Kenneth Heitke
2011-03-01 1:11 ` [RFC PATCH 5/5] RFC: msm: sps: Smart Peripheral System (SPS) driver Kenneth Heitke
2011-03-01 20:11 ` David Brown [this message]
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=8yahbbmvbwe.fsf@huya.qualcomm.com \
--to=davidb@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).